List a project's creator tasks
/v1/projects/{project}/creator-tasks in the Creator Tasks API.
curl "https://api.subscriby.net/v1/projects/$PROJECT_ID/creator-tasks?status=open" \ -H "Authorization: Bearer $SUBSCRIBY_TOKEN"status is open (the default: tasks not yet done whose grant still stands), completed, or all. Paged like every list but oldest first by default, so the longest-waiting member is at the top.
grant_idis the access ledger row the task belongs to; read it with the subscription's grants, where itsmodeiscreator_task.instructionsis the sentence the dashboard shows the creator, in the creator's locale.due_atis null for continuous access and the window's start for a dated pass.completed_atandcompleted_by_user_idare set once the task is done.
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.
uuidQuery Parameters
The tab: open (the default) lists tasks not yet done whose grant still stands, completed the ones marked done, all both.
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.
1 <= value1Rows per page, 1 to 100. A higher value clamps to the cap silently. Defaults to 25.
1 <= value <= 10025The column to order by. Defaults to created_at; a column the endpoint does not offer falls back to the default rather than failing.
"created_at"asc or desc. Defaults to asc.
"asc"Value in
- "asc"
- "desc"
Responses
200OKapplication/json
The page, oldest first by default.
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.
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.
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