Accept a workspace invite using its token
Redeems the invite token, creates the membership at the invited role, and returns the joined workspace; billable seats are re-synced afterwards. The caller must be authenticated with a synced profile and a verified email matching the invited address — an unverified or different email is refused. Unknown, already-closed, and expired invites are rejected.
Authorization
apiKey Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
curl -X POST "https://example.com/v1/workspace-invites/string/accept"{ "data": { "id": "string", "slug": "string", "name": "string", "icon": "initials", "accentColor": "string", "imageUrl": "string", "role": "owner", "permissions": [ "workspace:read" ], "createdAt": "string", "updatedAt": "string" }}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}{ "_tag": "ApiNotFound", "error": "not_found", "message": "That item does not exist, or this key cannot see it.", "status": 404}Preview a workspace invite from its token
Resolves an invite token to the workspace name, icon, accent color, invited email, role, and status so the sign-in screen can show what is being joined. No authentication; the token in the path is the credential. A pending invite past its expiry is reported with status `expired`, and an unknown token is not found.
Accept an invite from the caller's invite inbox
Same acceptance path as redeeming a token, but the invite is identified by id so the in-app invitations list does not need the token. The caller's verified email must still match the invited address, and unknown, already-closed, or expired invites are rejected.