members
POST /v1/members/invitations/{invitationId}/accept
Accept an invitation addressed to your email.
Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X POST https://api.zinndigital.com/v1/members/invitations/{invitationId}/accept \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Accepts an invitation whose email matches the **caller's verified email**, joining the organization with the invited role. The email match is the authorization — there is no secret token. Refuses an expired, revoked, already-accepted, or wrong-email invitation (422). Idempotent on the resulting membership.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
invitationId (path) | string | Yes | The invitation's id. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
id | string | Yes | — |
org_id | string | Yes | — |
org_name | string | Yes | The inviting organisation's display name, so an invitee can answer "accept?". |
email | string | Yes | — |
role | string | Yes | — |
site_grants | object[] | Yes | The individual sites this invitation lends, when it was created by sharing a site with an address that had no account (`POST /v1/sites/{siteId}/collaborators`). Empty for an ord… |
status | string<pending, accepted, revoked> | Yes | — |
expires_at | string | Yes | — |
accepted_at | string | No | — |
created_at | string | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422