---
title: "Complete a creator task"
method: POST
path: "/v1/projects/{project}/creator-tasks/{task}/complete"
tags: ["Creator Tasks"]
---

# Complete a creator task

`POST /v1/projects/{project}/creator-tasks/{task}/complete`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/projects/{project}/creator-tasks/{task}/complete`
- Auth: HTTP bearer

```bash
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.

## Path parameters

- `project` string, uuid, required
- `task` string, uuid, required

## Headers

- `Idempotency-Key` string, uuid, required

## Response `200`

200 with the completed task.

- object
  - `data` CreatorTaskResource, required: A creator task: a grant no connector can give, waiting for the creator to hand the perk over by hand.
    - `id` string, required: The task's id, the value the complete endpoint takes and `creator_task.opened` carries as `task_id`.
    - `grant_id` string, required: The access-ledger row the task belongs to; read it among the subscription's grants, where its `mode` is `creator_task`.
    - `project_id` string, required: The project the task belongs to.
    - `subscription_id` string, required: The purchase that entitles the member to the perk.
    - `subscriber_id` string, nullable, required: The member who is owed the perk.
    - `resource_id` string, required: The manual resource to hand over.
    - `resource_title` string, required: That resource's title, so an integration need not fetch it to say which perk.
    - `instructions` string, nullable, required: The sentence the dashboard shows the creator, in the creator's language.
    - `due_at` string, nullable, required: The window's start for a dated pass, ISO 8601; null for continuous access.
    - `completed_at` string, nullable, required: When the task was marked done, ISO 8601; null while open.
    - `completed_by_user_id` string, nullable, required: The creator who marked it done; null while open.
    - `created_at` string, nullable, required: When the task opened, ISO 8601.

## Other responses

- `400`: `IDEMPOTENCY_KEY_MISSING`: every write needs an `Idempotency-Key` header. Send a fresh UUID per distinct operation.
- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: 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.
- `404`: `RESOURCE_NOT_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.
- `409`: `IDEMPOTENCY_KEY_REUSED`: the key was already used in the last 24 hours with a different request body.
- `422`: `VALIDATION_FAILED`: 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.
- `425`: `IDEMPOTENCY_REPLAY_IN_PROGRESS`: the first request with this key is still running; retry in a few seconds and the original response is replayed.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)