Version
GET

Get a team member

/v1/teams/{team}/members/{member} in the Team Members API.

curl https://api.subscriby.net/v1/teams/$TEAM_ID/members/$USER_ID \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

One collaborator, with their email, which this route always includes because it requires team-member:view by definition. 404 RESOURCE_NOT_FOUND if the user is not on the team or the team is not in the caller's visibility set.

  • role_id points at a Role row on the same team, or null for the owner pseudo-row.
  • is_owner is true only for the single team creator; the owner is returned alongside the members but bypasses the membership table entirely.
GET
/v1/teams/{team}/members/{member}

Requires ability

The token must hold this ability, or the call is refused with 403.

Authorization

bearerToken
AuthorizationBearer <token>

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

team*string

The team, resolved by the route binder.

Formatuuid
member*string

The person's place on the team, resolved by the route binder.

Responses

200OK

The membership.

401Unauthorized

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

403Forbidden

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 found

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 requests

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