Me API
GET /v1/me is the first call a client makes.
GET /v1/me is the first call a client makes. It answers "who am I acting as?" in one round trip: the creator behind the token, the team the token is scoped to (the id every project call takes), every team they belong to, the platform plan and the capabilities it grants, the accounts linked on the connectors and where alerts go. The dashboard shows the same facts across Settings → Profile, Security and Notifications; a mobile or desktop client renders its home screen from this payload.
It lives under /v1/me with no project or team in the path because it is about the caller, never a project.
Endpoints
curl https://api.subscriby.net/v1/me \ -H "Authorization: Bearer $SUBSCRIBY_TOKEN"The caller's account; never paginated.
Read it once per session. Nothing here changes under a running client except by an action the client itself takes (linking an account, changing alert destinations, switching plan). Read it on sign-in and after those actions; there is no need to poll it.
planis the platform tier's type (free,starter,growth, …) while the subscription is active, ornullwithout one. It is the plan that gates what you can do, not the one still being billed while past due.capabilitieslists every capability the tiers can grant, eachtruewhen your plan or an active add-on grants it. The set is fixed by the platform, so a client can render toggles from the keys without knowing them in advance.current_teamis the team the token is scoped to (scope:team:<uuid>), when you still belong to it;nullwhen the token carries no team scope. Itsidis the value every project call resolves against.teamsis every team you own or are a member of, the same list asGET /v1/teams.identitiesis the same list asGET /v1/me/identities.alert_destinationsis the same list asGET /v1/me/alert-destinations;alert_destinations_defaultistruewhile no destination has been written and the default routing applies (every class to your primary connected account, critical classes by email).unread_notificationsis how many entries of your Notifications Center you have not opened, the number on the sidebar entry.
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
Responses
200OKapplication/json
The caller's account.
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.
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.
Related
How is this guide?