Sign in
auth

Get Signup Status

Where the caller's own self-serve setup stands.

This read creates nothing, mails nothing, and answers only about the caller's own address, so it leaks nothing the account's existence has not already committed to.

No account row exists until the verification link is redeemed, so a bare 404 there would tell a mid-verification return "you never signed up" while their link is still live — an outstanding link reports verification_pending instead, and only a truly unknown address 404s.

intent comes from the account when there is one and from the live link when there is not, which is the only place it exists before redemption. The page resends the verification mail from this answer, so a verification_pending read that reported no intent would have a buyer resend themselves a free signup.

get/api/v1/auth/signup/status

Response

Successful Response

status'verification_pending' | 'preparing' | 'ready' | 'failed' required
profile_collectedboolean
intent'free' | 'paid'

What a public signup is asking for.

PAID is what a buyer arriving from the pricing page carries. It is not a funding fact — nothing is charged until checkout, and the workspace opens on the same joining grant a free signup gets — so it decides exactly one thing, and this is the one statement of it that the rest of the codebase points at rather than restates: the workspace records WorkspaceOrigin.DIRECT_PAID rather than SELF_SERVE_DISCOVERY, which is what routes the account to checkout.

It exempts nothing. Signup is unconditional, so there is no admission for a buyer to be exempt from, and every abuse gate binds either way — a verified address, the rate limits and the disposable-domain block.

It is therefore not a privilege worth stealing: everything it unlocks is reachable through the free door by anyone the paid door would admit.

Changes

Changed in 3 of the 30 revisions of this API.4

  • 7720763f8bf12See the full diff
    • ○

      removed the paused enum value from the response property for the response status

      response-property-enum-value-removed

    • ○

      removed the waitlisted enum value from the response property for the response status

      response-property-enum-value-removed

    This revision also has 13 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 924eeadc29ad1See the full diff
    • ○

      added the optional property to the response with the status

      response-optional-property-added

  • b61a1454aad61See the full diff
    • ○

      endpoint added

      endpoint-added