DocsAPI reference

Preview invitation

What the acceptance page may show before anybody has signed in.

get/api/auth/invitation
Authentication
None
Retries
Safe to repeat
Body
None
Version
2026-09-03

A GET with the token in the query string, because the recipient arrives by clicking a link. That does put the token in browser history and in any referrer the page leaks - which is why it is single-use, expires in seven days, and why the page should exchange it for a session promptly.

Query parameters#

  • tokenstringrequired

Responses#

  • 200OKapplication/json

    InvitationPreview

    • emailstringrequired
    • expires_atstring (date-time)required
    • organization_namestringrequired
    • organization_slugstringrequired
    • roleOrgRole | stringrequired
    • has_accountboolean

      Default: false

    • invited_bystring | null
    5 response headers
    RateLimit-Limit

    Requests permitted in the current window.

    RateLimit-Remaining

    Requests left in the current window. Back off before it reaches 0.

    RateLimit-Reset

    Seconds until the current window resets.

    X-API-Version

    The dated version of the API contract that served this response, e.g. 2026-09-03. Pin against it; it changes only when a response shape changes incompatibly.

    X-Request-ID

    Quote this in a support request to identify the call.

  • 422Validation error

    The shared error envelope, served as application/problem+json with error.code set to validation_error. Its details name each field that failed and why.

Errors#

Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:

  • validation_error · 422 — The payload was well-formed JSON but failed schema validation.
  • rate_limited · 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-agent limit on top.

More Auth endpoints#

Something unclear or missing? Tell us and we’ll fix it.