Members API

Members are the project-scoped subscribers. Every payment is made on behalf of a member; every access grant a connector issues resolves to one. These endpoints list and read them, flip the three moderation states (ban, unban, kick) and manage the accounts a member has connected on the connectors.

Endpoints

GET/v1/projects/{project}/membersList a project's members GET/v1/projects/{project}/members/{member}Get a member GET/v1/projects/{project}/members/{member}/identitiesList a member's connected accounts POST/v1/projects/{project}/members/{member}/banBan a member POST/v1/projects/{project}/members/{member}/kickKick a member POST/v1/projects/{project}/members/{member}/unbanUnban a member DELETE/v1/projects/{project}/members/{member}/identities/{link}Disconnect a member's account

List a project's members

GET

curl "https://api.subscriby.net/v1/projects/$PROJECT_ID/members?status=customer" \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

Newest first, paged with page and per_page (default 25; limit is accepted as an alias). status narrows to one lifecycle state. identity looks one member up by the account they connected, connector:external_id, for a workflow that starts from a platform event and needs the member behind an account id; the page then holds that one member with their identities embedded, or no rows.

Requires ability

project-user:view-any

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

MCP tools

find_member_by_identity list_subscribers

Run the same action from an agent, behind the same ability.

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

project*string

The project, resolved by the route binder.

Formatuuid

Query Parameters

status?|

Narrow the page to one lifecycle state: lead, trialing, customer, churned or banned. Any other value is refused rather than answered with an empty page, so a typo in an automation is noticed.

identity?|

Find the member who connected a given account: the connector key and the platform's own id for the account joined by a colon, connector:123456789. The page then holds that one member with their identities embedded, or no rows when nobody in the project connected that account. A value with no connector before the colon is refused.

Match^[a-z0-9][a-z0-9-]*:\S+$

Lengthlength <= 255

page?integer

The 1-based page to return. A page past the last answers an empty data array with meta.total still filled, so a loop can stop without guessing.

Range1 <= value

Default1

per_page?integer

Rows per page, 1 to 100. A higher value clamps to the cap silently. Defaults to 25.

Range1 <= value <= 100

Default25

sort_by?string

The column to order by. Defaults to created_at; a column the endpoint does not offer falls back to the default rather than failing.

Default"created_at"

sort_direction?string

asc or desc. Defaults to desc.

Default"desc"

Value in

"asc"
"desc"

limit?integer

Legacy alias of per_page, kept for clients that predate it. per_page wins when both are sent.

Range1 <= value <= 100

Responses

200OKapplication/json

The page, newest first; one row or none when narrowed to an account, with its connected accounts embedded.

data*array<>

The items on this page.

links*

Links to the first, last, previous and next pages.

meta*

The paging counters for this page.

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).

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

422Validation failedVALIDATION_FAILEDapplication/json

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when status is not one of the five states, or identity has no connector before the colon.

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/members"

{  "data": [    {      "id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",      "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",      "username": "@janedoe",      "first_name": "Jane",      "last_name": "Doe",      "email": null,      "billing_email": "[email protected]",      "identities": [        {          "id": "6a1f0c3e-2d4b-4e8a-9c7d-1b5e3f9a2c4d",          "connector": "telegram",          "source": "handshake",          "preferred": true,          "notify": false,          "external_id": "123456789",          "display_name": "Jane Doe",          "username": "janedoe",          "linked_at": "2026-05-18T10:05:00Z"        }      ],      "status": "customer",      "joined_at": "2026-05-18T10:05:00Z",      "created_at": "2026-05-18T10:05:00Z",      "updated_at": "2026-05-18T10:05:00Z"    }  ],  "links": {    "first": "string",    "last": "string",    "prev": "string",    "next": "string"  },  "meta": {    "current_page": 1,    "from": 1,    "last_page": 1,    "links": [      {        "url": "string",        "label": "string",        "active": true      }    ],    "path": "string",    "per_page": 0,    "to": 1,    "total": 0  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: MemberResource[];  links: Links;  meta: Meta;}export interface MemberResource {  id: string;  project_id: string;  username: string;  first_name: string;  last_name: string;  email?: string | null;  billing_email?: string | null;  identities?: MemberIdentityResource[];  status: string | "lead" | "trialing" | "customer" | "churned" | "banned";  joined_at: string | null;  created_at: string | null;  updated_at: string | null;}export interface MemberIdentityResource {  id: string;  connector: string;  source: string;  preferred: boolean;  notify: boolean;  external_id: string;  display_name: string | null;  username: string | null;  linked_at: string;}export interface Links {  first: string | null;  last: string | null;  prev: string | null;  next: string | null;}export interface Meta {  current_page: number;  from: number | null;  last_page: number;  links: Link[];  path: string | null;  per_page: number;  to: number | null;  total: number;}export interface Link {  url: string | null;  label: string;  active: boolean;}

Get a member

GET

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

project-user:view

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

MCP tool

get_subscriber

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

member*string

The member, resolved within the project by the route binder.

Formatuuid

Responses

200OKapplication/json

The member.

data*

The response's payload.

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).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/members/497f6eca-6276-4993-bfeb-53cbbbba6f08"

{  "data": {    "id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "username": "@janedoe",    "first_name": "Jane",    "last_name": "Doe",    "email": null,    "billing_email": "[email protected]",    "status": "customer",    "joined_at": "2026-05-18T10:05:00Z",    "created_at": "2026-05-18T10:05:00Z",    "updated_at": "2026-05-18T10:05:00Z",    "identities": [      {        "id": "6a1f0c3e-2d4b-4e8a-9c7d-1b5e3f9a2c4d",        "connector": "telegram",        "source": "handshake",        "preferred": true,        "notify": false,        "external_id": "123456789",        "display_name": "Jane Doe",        "username": "janedoe",        "linked_at": "2026-05-18T10:05:00Z"      }    ]  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: Data;}export interface Data {  id: string;  project_id: string;  username: string;  first_name: string;  last_name: string;  email?: string | null;  billing_email?: string | null;  identities: MemberIdentityResource[];  status: string | "lead" | "trialing" | "customer" | "churned" | "banned";  joined_at: string | null;  created_at: string | null;  updated_at: string | null;}export interface MemberIdentityResource {  id: string;  connector: string;  source: string;  preferred: boolean;  notify: boolean;  external_id: string;  display_name: string | null;  username: string | null;  linked_at: string;}

List a member's connected accounts

GET

curl https://api.subscriby.net/v1/projects/$PROJECT_ID/members/$MEMBER_ID/identities \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

The member's connected accounts, preferred first. Never paginated. A member can connect one account per platform the project is on, from the portal's Account & Recovery screen or by talking to the project's bot; the member read embeds the same rows as identities. Connecting has no endpoint: it is a two-sided proof the member completes on the connector.

id is the link, which is what the disconnect endpoint takes; external_id is the platform's own id for the account.
source says how the link was proven: handshake (connected from the portal and confirmed by the bot, or a portal sign-in), adopted (taken over from another of the creator's projects), portal, bot (the bot met the account first) or backfill (migrated from before connectors).
preferred marks the account the project reaches first; a member's first account is, and the member can move it on the portal.
notify marks a further account the member switched the project's notices on for, from the portal. The preferred account always hears them, so it reads false there too; a grant notice stays on the connector of the grant and a support reply on the connector the member wrote from, whatever the switches say.

Requires ability

project-user:view

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

MCP tool

list_member_identities

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the binder.

Formatuuid

member*string

The member, resolved within the project.

Formatuuid

Responses

200OKapplication/json

Array of MemberIdentityResource

data*array<>

The items.

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).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/members/497f6eca-6276-4993-bfeb-53cbbbba6f08/identities"

{  "data": [    {      "id": "6a1f0c3e-2d4b-4e8a-9c7d-1b5e3f9a2c4d",      "connector": "telegram",      "source": "handshake",      "preferred": true,      "notify": false,      "external_id": "123456789",      "display_name": "Ada Lovelace",      "username": "ada",      "linked_at": "2026-09-12T10:05:00Z"    }  ]}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: MemberIdentityResource[];}export interface MemberIdentityResource {  id: string;  connector: string;  source: string;  preferred: boolean;  notify: boolean;  external_id: string;  display_name: string | null;  username: string | null;  linked_at: string;}

Ban a member

POST

curl -X POST https://api.subscriby.net/v1/projects/$PROJECT_ID/members/$MEMBER_ID/ban \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \  -H "Idempotency-Key: $(uuidgen)" \  -H "Content-Type: application/json" \  -d '{"reason": "Repeated spam in the research channel."}'

Moves a lead, customer, trialing or churned member to banned, removes their access on every connector and emits member.banned with the optional reason. Answers 200 with the member; a member already banned is answered unchanged and emits nothing.

Connector-side eviction (kicks from the gated spaces, revoked invite links) runs asynchronously on the connector pipeline after the flip. The call returns as soon as Subscriby's state has been updated and the webhook event has been fired; the platform actions complete in the background.

Requires ability

project-user:update

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

Fires one event

member.banned

Delivered to every endpoint subscribed to it once the change is made.

MCP tool

ban_member

Runs the same action from an agent, behind the same ability.

Idempotent

Idempotency-Key

Send the header on every call; the same key replays the original response for 24 hours.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

member*string

The member, resolved within the project by the route binder.

Formatuuid

Header Parameters

Idempotency-Key*string

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Formatuuid

Request body

JSONWhat the request carriesOptionalapplication/json

reason?string

Why the member is banned; carried on the member.banned event and shown in the dashboard, never sent to the member.

Responses

200OKapplication/json

The member after the change.

data*

The response's payload.

400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

error*

The one envelope every failure uses.

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).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json

The key was already used in the last 24 hours with a different request body.

error*

The one envelope every failure uses.

422Validation failedVALIDATION_FAILEDapplication/json

error*

The one envelope every failure uses.

425Too earlyIDEMPOTENCY_REPLAY_IN_PROGRESSapplication/json

The first request with this key is still running; retry in a few seconds and the original response is replayed.

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X POST "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/members/497f6eca-6276-4993-bfeb-53cbbbba6f08/ban" \  -H "Idempotency-Key: 0199a4ae-6c02-7b5c-9f51-c5f0da5e2f12" \  -H "Content-Type: application/json" \  -d '{}'

{  "data": {    "id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "username": "@janedoe",    "first_name": "Jane",    "last_name": "Doe",    "email": null,    "billing_email": "[email protected]",    "identities": [      {        "id": "6a1f0c3e-2d4b-4e8a-9c7d-1b5e3f9a2c4d",        "connector": "telegram",        "source": "handshake",        "preferred": true,        "notify": false,        "external_id": "123456789",        "display_name": "Jane Doe",        "username": "janedoe",        "linked_at": "2026-05-18T10:05:00Z"      }    ],    "status": "customer",    "joined_at": "2026-05-18T10:05:00Z",    "created_at": "2026-05-18T10:05:00Z",    "updated_at": "2026-05-18T10:05:00Z"  }}

Type definitions

The shapes above as types, ready to paste into your client.

Request

export interface Request {  reason?: string;}

Response

export interface Response {  data: MemberResource;}export interface MemberResource {  id: string;  project_id: string;  username: string;  first_name: string;  last_name: string;  email?: string | null;  billing_email?: string | null;  identities?: MemberIdentityResource[];  status: string | "lead" | "trialing" | "customer" | "churned" | "banned";  joined_at: string | null;  created_at: string | null;  updated_at: string | null;}export interface MemberIdentityResource {  id: string;  connector: string;  source: string;  preferred: boolean;  notify: boolean;  external_id: string;  display_name: string | null;  username: string | null;  linked_at: string;}

Kick a member

POST

Moves the member to churned, removes them from every resource and emits member.kicked with the optional reason. Unlike a ban, a kicked member may come back by subscribing again. Answers 200 with the member; a banned member is answered unchanged, since a ban already says more. As with a ban, the connector-side eviction completes in the background after the call returns.

Requires ability

project-user:update

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

Fires one event

member.kicked

Delivered to every endpoint subscribed to it once the change is made.

MCP tool

kick_member

Runs the same action from an agent, behind the same ability.

Idempotent

Idempotency-Key

Send the header on every call; the same key replays the original response for 24 hours.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

member*string

The member, resolved within the project by the route binder.

Formatuuid

Header Parameters

Idempotency-Key*string

Formatuuid

Request body

JSONWhat the request carriesOptionalapplication/json

reason?string

Why the member is removed; carried on the member.kicked event and shown in the dashboard, never sent to the member.

Responses

200OKapplication/json

The member after the change.

data*

The response's payload.

400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

error*

The one envelope every failure uses.

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).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json

The key was already used in the last 24 hours with a different request body.

error*

The one envelope every failure uses.

422Validation failedVALIDATION_FAILEDapplication/json

error*

The one envelope every failure uses.

425Too earlyIDEMPOTENCY_REPLAY_IN_PROGRESSapplication/json

The first request with this key is still running; retry in a few seconds and the original response is replayed.

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X POST "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/members/497f6eca-6276-4993-bfeb-53cbbbba6f08/kick" \  -H "Idempotency-Key: 0199a4ae-6c02-7b5c-9f51-c5f0da5e2f12" \  -H "Content-Type: application/json" \  -d '{}'

{  "data": {    "id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "username": "@janedoe",    "first_name": "Jane",    "last_name": "Doe",    "email": null,    "billing_email": "[email protected]",    "identities": [      {        "id": "6a1f0c3e-2d4b-4e8a-9c7d-1b5e3f9a2c4d",        "connector": "telegram",        "source": "handshake",        "preferred": true,        "notify": false,        "external_id": "123456789",        "display_name": "Jane Doe",        "username": "janedoe",        "linked_at": "2026-05-18T10:05:00Z"      }    ],    "status": "customer",    "joined_at": "2026-05-18T10:05:00Z",    "created_at": "2026-05-18T10:05:00Z",    "updated_at": "2026-05-18T10:05:00Z"  }}

Type definitions

The shapes above as types, ready to paste into your client.

Request

export interface Request {  reason?: string;}

Response

export interface Response {  data: MemberResource;}export interface MemberResource {  id: string;  project_id: string;  username: string;  first_name: string;  last_name: string;  email?: string | null;  billing_email?: string | null;  identities?: MemberIdentityResource[];  status: string | "lead" | "trialing" | "customer" | "churned" | "banned";  joined_at: string | null;  created_at: string | null;  updated_at: string | null;}export interface MemberIdentityResource {  id: string;  connector: string;  source: string;  preferred: boolean;  notify: boolean;  external_id: string;  display_name: string | null;  username: string | null;  linked_at: string;}

Unban a member

POST

Moves a banned member to churned and emits member.unbanned. Access is not restored: the member subscribes again from the portal or the bot. Answers 200 with the member; a member who is not banned is answered unchanged and emits nothing.

Requires ability

project-user:update

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

Fires one event

member.unbanned

Delivered to every endpoint subscribed to it once the change is made.

MCP tool

unban_member

Runs the same action from an agent, behind the same ability.

Idempotent

Idempotency-Key

Send the header on every call; the same key replays the original response for 24 hours.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

member*string

The member, resolved within the project by the route binder.

Formatuuid

Header Parameters

Idempotency-Key*string

Formatuuid

Responses

200OKapplication/json

The member after the change.

data*

The response's payload.

400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

error*

The one envelope every failure uses.

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).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json

The key was already used in the last 24 hours with a different request body.

error*

The one envelope every failure uses.

425Too earlyIDEMPOTENCY_REPLAY_IN_PROGRESSapplication/json

The first request with this key is still running; retry in a few seconds and the original response is replayed.

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X POST "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/members/497f6eca-6276-4993-bfeb-53cbbbba6f08/unban" \  -H "Idempotency-Key: 0199a4ae-6c02-7b5c-9f51-c5f0da5e2f12"

{  "data": {    "id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "username": "@janedoe",    "first_name": "Jane",    "last_name": "Doe",    "email": null,    "billing_email": "[email protected]",    "identities": [      {        "id": "6a1f0c3e-2d4b-4e8a-9c7d-1b5e3f9a2c4d",        "connector": "telegram",        "source": "handshake",        "preferred": true,        "notify": false,        "external_id": "123456789",        "display_name": "Jane Doe",        "username": "janedoe",        "linked_at": "2026-05-18T10:05:00Z"      }    ],    "status": "customer",    "joined_at": "2026-05-18T10:05:00Z",    "created_at": "2026-05-18T10:05:00Z",    "updated_at": "2026-05-18T10:05:00Z"  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: MemberResource;}export interface MemberResource {  id: string;  project_id: string;  username: string;  first_name: string;  last_name: string;  email?: string | null;  billing_email?: string | null;  identities?: MemberIdentityResource[];  status: string | "lead" | "trialing" | "customer" | "churned" | "banned";  joined_at: string | null;  created_at: string | null;  updated_at: string | null;}export interface MemberIdentityResource {  id: string;  connector: string;  source: string;  preferred: boolean;  notify: boolean;  external_id: string;  display_name: string | null;  username: string | null;  linked_at: string;}

Disconnect a member's account

DELETE

curl -X DELETE https://api.subscriby.net/v1/projects/$PROJECT_ID/members/$MEMBER_ID/identities/$LINK_ID \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \  -H "Idempotency-Key: $(uuidgen)"

Disconnects an account on the creator's behalf, the counterpart of the member's own Disconnect on the portal: it no longer signs the member in and the bot no longer knows them by it. Answers an empty 204 and emits member.identity_unlinked.

Requires ability

project-user:update

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

Fires one event

member.identity_unlinked

Delivered to every endpoint subscribed to it once the change is made.

MCP tool

unlink_member_identity

Runs the same action from an agent, behind the same ability.

Idempotent

Idempotency-Key

Send the header on every call; the same key replays the original response for 24 hours.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the binder.

Formatuuid

member*string

The member, resolved within the project.

Formatuuid

link*string

The member's link, resolved within the member.

Formatuuid

Header Parameters

Idempotency-Key*string

Formatuuid

Responses

204No content

No content

400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

error*

The one envelope every failure uses.

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).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json

The key was already used in the last 24 hours with a different request body.

error*

The one envelope every failure uses.

422Validation failedVALIDATION_FAILEDapplication/json

When the account is the member's last way to sign in (no verified email, linked Google account or other connected account remains).

error*

The one envelope every failure uses.

425Too earlyIDEMPOTENCY_REPLAY_IN_PROGRESSapplication/json

The first request with this key is still running; retry in a few seconds and the original response is replayed.

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X DELETE "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/members/497f6eca-6276-4993-bfeb-53cbbbba6f08/identities/497f6eca-6276-4993-bfeb-53cbbbba6f08" \  -H "Idempotency-Key: 0199a4ae-6c02-7b5c-9f51-c5f0da5e2f12"

No body on this response.

Subscriptions APIThe purchases a member holds.Support Inbox APIA block there is an inbox decision, not a moderation one.member.* eventsThe endpoints below announce banned, unbanned, kicked and identity_unlinked; identity_linked fires when a member connects an account, and the rest of the family (joined, trial_joined, converted, churned, removed, resource_added, resource_pending, resource_removed) comes from upstream flows.

Members API

EndpointsCopy Anchor Link

List a project's membersCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Query ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Get a memberCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

ResponsesCopy Anchor Link

List a member's connected accountsCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Ban a memberCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Header ParametersCopy Anchor Link

Request bodyCopy Anchor Link

ResponsesCopy Anchor Link

Kick a memberCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Header ParametersCopy Anchor Link

Request bodyCopy Anchor Link

ResponsesCopy Anchor Link

Unban a memberCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Header ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Disconnect a member's accountCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Header ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Related

On this page

Endpoints

List a project's members

Authorization

Path Parameters

Query Parameters

Responses

Get a member

Authorization

Path Parameters

Responses

List a member's connected accounts

Authorization

Path Parameters

Responses

Ban a member

Authorization

Path Parameters

Header Parameters

Request body

Responses

Kick a member

Authorization

Path Parameters

Header Parameters

Request body

Responses

Unban a member

Authorization

Path Parameters

Header Parameters

Responses

Disconnect a member's account

Authorization

Path Parameters

Header Parameters

Responses