Get a member
/v1/projects/{project}/members/{member} in the Members API.
One member with their connected accounts embedded as identities.
email and billing_email are present only when the calling token carries project-user:view, which this route requires; a roster-only token (project-user:view-any) never sees them on the list, where the keys are absent, not null. The two are not interchangeable:
| Field | Where it comes from | Safe to contact? |
|---|---|---|
email | The member chose it themselves and verified it. It is their portal sign-in credential. | Yes |
billing_email | Whatever address they gave a payment provider at checkout. Never verified, never used for authentication. | Treat as identification only |
Members join through a bot and are never asked for an email, so for most of them email is null and billing_email is the only address on record, which is what makes it useful for matching a refund request to a subscription.
billing_email is populated automatically from the payment provider on every new payment (Stripe, PayPal, Paystack, Razorpay and Skrill). Members who last paid before that capture existed may have null until their next payment, and members who joined by redeeming an access code never had a payment at all, so they have no billing address to record.
Requires ability
The token must hold this ability, or the call is refused with 403.
MCP tool
Runs the same action from an agent, behind the same ability.
Authorization
bearerToken A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.
In: header
Path Parameters
The project, resolved by the route binder.
uuidThe member, resolved within the project by the route binder.
uuidResponses
200OKapplication/json
The member.
401UnauthorizedAUTHENTICATION_REQUIREDapplication/json
The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).
403ForbiddenTOKEN_MISSING_ABILITYapplication/json
The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers FORBIDDEN, TEAM_TIER_REQUIRED or CONNECTOR_TIER_REQUIRED with the same status, and says so in its own description.
404Not foundRESOURCE_NOT_FOUNDapplication/json
An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
429Too many requestsRATE_LIMITEDapplication/json
The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.
How is this guide?
Last updated on