---
title: "The creator marked a manual perk as handed over; the grant is issued."
method: POST
path: "creator_task.completed"
tags: ["creator_task.* events"]
---

# The creator marked a manual perk as handed over; the grant is issued.

`POST creator_task.completed` (webhook)

### When this fires

The creator (or a teammate, an integration or an agent on their behalf) marks a creator task done: on the members page, through [the complete endpoint](https://docs.subscriby.net/api/v1/reference/creator-tasks) or the MCP tool [`complete_creator_task`](https://docs.subscriby.net/mcp/v1/tools/creator-task/complete-creator-task). The access ledger row moves from `pending` to `granted`, this event says who did it, and `member.resource_added` follows for the same `grant_id` with mode `creator_task`.

### Caveats

- Completing a task is not idempotent over the API: a second call for a completed task answers `422 VALIDATION_FAILED`.
- The member is not messaged by a bot on completion; tell them yourself, or let the portal show the perk as delivered.

### Related events

- `creator_task.opened`: the task being done.
- `member.resource_added`: raised for the same grant on completion.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'creator_task.completed', required: The event name, always `creator_task.completed` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `task_id` string, uuid, required: The task that was completed.
    - `grant_id` string, uuid, required: The access ledger row, now `granted`.
    - `subscription_id` string, uuid, required: Subscription that entitles the member.
    - `subscriber_id` string, uuid, required: Subscriber's project-scoped user id.
    - `resource_id` string, uuid, required: The manual resource.
    - `resource_kind` string, required: Always `manual`: only a manual perk opens a creator task.
    - `completed_at` string, date-time, required: When it was marked done.
    - `completed_by_user_id` string, uuid, required: The creator or teammate who marked it done.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

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