POST

Complete a creator task

/v1/projects/{project}/creator-tasks/{task}/complete in the Creator Tasks API.

curl -X POST https://api.subscriby.net/v1/projects/$PROJECT_ID/creator-tasks/$TASK_ID/complete \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \  -H "Idempotency-Key: $(uuidgen)"

Marks the task done by the token's user, moves the grant to granted, and raises creator_task.completed followed by member.resource_added for the same grant. Answers 200 with the completed task.

Nobody messages the member for you. A manual perk is yours to hand over. Completing the task records that you did and tells your integrations; it does not send the member anything.

Requires ability

project-subscription:update

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

Fires events

creator_task.completed member.resource_added

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

MCP tool

complete_creator_task

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>

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

task*string

The task, 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

Responses

200OKapplication/json

200 with the completed task.

400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json

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

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.

409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json

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

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 the task is already done, or its purchase has since ended so there is nothing left to grant; error.context.task_id names it.

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.

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.

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/creator-tasks/497f6eca-6276-4993-bfeb-53cbbbba6f08/complete" \  -H "Idempotency-Key: 0199a4ae-6c02-7b5c-9f51-c5f0da5e2f12"

{  "data": {    "id": "9e4b2c71-3d58-4a6f-b0e2-7c1d5f8a9b34",    "grant_id": "7d1c3e9a-2b64-4f0e-9a58-3c6b1d8e2f47",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "subscription_id": "5b7e2d40-1a86-4c39-97f2-e83d0b16c5a4",    "subscriber_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",    "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",    "resource_title": "Welcome packet",    "instructions": "Give Ada Lovelace access to Welcome packet.",    "due_at": null,    "completed_at": null,    "completed_by_user_id": null,    "created_at": "2026-09-12T10:05:30Z"  }}

Type definitions

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

export interface Response {  data: CreatorTaskResource;}export interface CreatorTaskResource {  id: string;  grant_id: string;  project_id: string;  subscription_id: string;  subscriber_id: string | null;  resource_id: string;  resource_title: string;  instructions: string | null;  due_at: string | null;  completed_at: string | null;  completed_by_user_id: string | null;  created_at: string | null;}

How is this guide?

Last updated on October 3, 2026 at 05:57 UTC

List a project's creator tasks

/v1/projects/{project}/creator-tasks in the Creator Tasks API.

Disaster Recovery API

Everything the Disaster Recovery pages show a creator is readable here: what the health probes found broken, what was done about it and whether it can still be undone, how many members a channel recovery has re-admitted so far, how many self-service recoveries the rolling window still allows, and how ready the account is for the next ban.