---
title: "A purchase entitles a subscriber to a manual perk, so the creator has something to do by hand."
method: POST
path: "creator_task.opened"
tags: ["creator_task.* events"]
---

# A purchase entitles a subscriber to a manual perk, so the creator has something to do by hand.

`POST creator_task.opened` (webhook)

### When this fires

A subscription becomes active (or a pass window opens) on a plan that includes a **manual** resource: a perk no connector can give, which the creator hands over themselves. The access ledger records a `creator_task` grant in state `pending` and opens a task naming the member and the perk; this event carries that task. One event per manual resource the purchase entitles the member to. Nothing is sent to the member by a bot for a manual perk; the portal shows the perk as arranged by the organiser.

### Caveats

- A task is opened once per purchase, resource and window; a retry of the granting job does not open a second one.
- A purchase that ends before the task is done revokes the grant; the task then drops out of the open list without a `creator_task.completed`.

### Related events

- `creator_task.completed`: the task is done and the grant issued.
- `member.resource_added`: raised for the same `grant_id` 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.opened', required: The event name, always `creator_task.opened` 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; what [the complete endpoint](https://docs.subscriby.net/api/v1/reference/creator-tasks) takes.
    - `grant_id` string, uuid, required: The access ledger row, in state `pending` with mode `creator_task`.
    - `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.
    - `instructions` string, required: What the creator has to do, in the creator's locale: the member's name and the perk.
    - `due_at` string, date-time, nullable, required: When the perk is due; null for continuous access, the window's start for a dated pass.

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