Version
WEBHOOK

creator_task.completed

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

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 or the MCP tool 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.

Ability to subscribe

A token needs this to subscribe an endpoint to the event.

Header Parameters

SB-Signature*string

t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.

SB-Event-Id*string

The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.

SB-Event-Name*string

The event name, the same as the envelope's type.

Content-Type*string

Always application/json.

User-Agent*string

Always Subscriby-Webhooks/1.0.

Payload

JSONWhat Subscriby posts to your endpoint

The signed JSON envelope posted to your endpoint.

The envelope every event is delivered in.

Responses

2XXAny success status

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

defaultAny other status

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.

How is this guide?

Last updated on