Invite a member into an organization
/api/v1/organizations/{id}/invitesInvites an email into the organization. role_id is held on acceptance at node_id, the organization node (the default) or an office or team beneath it, for the effective_from to effective_to window when given; with no role_id the invitation admits a member holding nothing, which only the organization node allows (400 invite.malformed_assignment beneath it). Acceptance creates what is missing in one transaction: the identity, its Environment membership, the organization membership and the role. For someone who already holds an active membership in this Environment the invitation is a request to join (intent: grant): accepting is their consent, proven by their password or their own sign-in. Requires the identity.manage permission, or canopy:organization.manage at the organization or canopy:access.manage at the place for the organization's own administrators, and emits invite.created.
Authentication
Authorization Option A JWT access token. Never send alongside X-API-Key: a request carrying both is refused.
X-API-Key Option B API key for management-tier access. Never send alongside an Authorization header: a request carrying both is refused.
Path Parameters
idstring Required Request body
application/json
emailstring Required Email to invite. Works for people with no identity in this Environment — one is created when they accept.
role_idstring Optional The role the person holds on acceptance, at `node_id`. Optional at the organization node, where accepting admits a member with no role; required for a place beneath it.
node_idstring Optional Where the role is held: the organization node (the default) or an office or team beneath it. Accepting admits the person to the organization either way.
effective_fromstring · date-time Optional When the role starts to count (ISO 8601). Copied onto the assignment the invitation grants; needs a role.
effective_tostring · date-time Optional When the role stops counting (ISO 8601), after `effective_from`. Copied onto the assignment; an invitation whose window has ended by acceptance is refused with `400 invite.window_ended`.
first_namestring Optional last_namestring Optional send_emailboolean Optional Set false to skip the email and deliver the returned accept URL yourself.
Responses
application/json
data *ApiIdentityInviteResponseDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
Errors
When the request can't be completed, the response body includes a stable error code you can branch on, and a correlation_id (also sent as the X-Correlation-Id header). Quote the correlation id when you contact support: it identifies the exact request in Canopy's logs.
assignment.grant_ceilingForbiddenThe caller is an identity (a customer's own administrator, acting with its session token) granting a role it may not: the role carries a permission the caller does not hold at the target node or above. Applies to creating an assignment (the organization's assignments route included), changing an assignment's role, and creating an invitation that carries a role. Console users, API keys, and the organization's own administrator inside its organization are never bounded; removing an assignment never is.
Grant a role whose every permission the caller holds at that node, read the roles the caller may grant from <code>GET /api/v1/organizations/{id}/nodes/{nodeId}/grantable-roles</code> and offer only those, or make the change with your API key.
Returned object
curl -X POST "https://auth.canopy-io.com/api/v1/organizations/value/invites" \ -H "X-API-Key: $CANOPY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "email": "string", "role_id": "string", "node_id": "string", "effective_from": "2026-04-20T12:00:00.000Z", "effective_to": "2026-04-20T12:00:00.000Z", "first_name": "string", "last_name": "string", "send_email": true }'
{ "data": { "id": "string", "email": "string", "intent": "activate", "first_name": "string", "last_name": "string", "name": "string", "role_id": "string", "node_id": "string", "node_name": "string", "organization_node_id": "string", "effective_from": "2026-04-20T12:00:00.000Z", "effective_to": "2026-04-20T12:00:00.000Z", "has_initial_assignment": false, "status": "pending", "expires_at": "2026-04-20T12:00:00.000Z", "invited_by": "string", "invited_by_identity_id": "string", "created_at": "2026-04-20T12:00:00.000Z", "accept_url": "string" } }
Tell us how we can improve this guide.