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`.
/v1/invites/{invite}/acceptOne 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 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
The invite's id
^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"}Accept an invite POST
As the person it was sent to: signed in at Synq with that email, verified. Recorded as `invite.accepted` and `member.added`.
Read what an invite offers POST
What an invite's link offers, while it can still be accepted: the org's name, the role across the org and the brand roles, each with what it lets the person do and each brand by its name, who sent it and when it stops working, for the page that asks before accepting. Public: it needs no credential, and the token is in the body, never the URL. It answers nothing else about the org, nor the address the invite was sent to. A few a minute from one address, or from one person signed in.