A creator registers a new project.
When this fires
A creator registers a new project. The event lands the moment the new project becomes available for further configuration.
The project description is not included in the snapshot. Fetch it with the project endpoint if you need it.
Caveats
- Use the SB-Event-Id header to dedupe deliveries; it carries the same ULID as id, without the evt_ prefix.
- project.created fires only for projects created through the REST API or MCP; projects created in the dashboard emit no project.created, so it is not guaranteed to be the first event you see for a project_id. Subsequent events on the same project may interleave.
- Archived/restored states are a separate event pair: listen for project.archived and project.restored rather than relying on data.project.active flipping inside project.updated.
Related events
- project.updated: fires on subsequent mutable-field changes.
- project.archived: paired with project.restored for soft-disable transitions.
Headers
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=.
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.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
Response
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.