project.created

When this fires

A creator registers a new project. The event lands the moment the new project becomes available for further configuration.

Required ability

project:view — token must carry this at mint time to subscribe an endpoint to this event.

Payload

{
  "id": "evt_01HX...",
  "type": "project.created",
  "created_at": "2026-05-18T10:05:00Z",
  "api_version": "2026-05-01",
  "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
  "data": {
    "project": {
      "id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
      "name": "Research Premium",
      "handle": "research-premium",
      "active": true,
      "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86"
    }
  }
}

Field reference

Field	Type	Notes
`id`	string ULID	Unique event id, prefixed `evt_`. Use for idempotent processing.
`type`	string	Always `project.created` for this event.
`created_at`	ISO 8601 timestamp	Server-side emission time.
`api_version`	string	Webhook API contract version.
`project_id`	string UUID	Project this event belongs to.
`data.project.id`	string UUID	Project identifier; matches the top-level `project_id`.
`data.project.name`	string	Display name shown in the dashboard and on `my.subscriby.net/...`.
`data.project.handle`	string	URL slug for the public landing page.
`data.project.active`	boolean	Always `true` at creation; flips on archive / restore.
`data.project.team_id`	string UUID	Team that owns the project (a personal team for solo creators).

The project description is not included in the snapshot. Fetch it with GET /v1/projects/{project} 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.

project.updated — fires on subsequent mutable-field changes.
project.archived — paired with project.restored for soft-disable transitions.
Project events overview — back to family overview.