SynqDocs
Management APIInvites

Accept an invite waiting for you

One of the signed-in person's own pending invites (`GET /v1/invites`), by its id: their verified email address is the invite's, which proves it was sent to them. An invite to anyone else is 404, as one that never was. Recorded as `invite.accepted` and `member.added`.

POST/v1/invites/{invite}/accept

One of the signed-in person's own pending invites (GET /v1/invites), by its id: their verified email address is the invite's, which proves it was sent to them. An invite to anyone else is 404, as one that never was. Recorded as invite.accepted and member.added.

Authorization

bearer
AuthorizationBearer <token>

An org API key (sk_live_…, sk_test_…), or an access token from the Synq issuer (the synq brand, on the accounts host) for this API.

In: header

Path Parameters

invite*string

The invite's id

Match^inv_[0-9a-hjkmnp-tv-z]{26}$

Response Body

application/json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

curl -X POST "https://api.synq.build/v1/invites/inv_01h455vb4pex5vsknk084sn02q/accept" \  -H "Authorization: Bearer $SYNQ_API_KEY"
{  "org_id": "org_01h455vb4pex5vsknk084sn02q"}