---
title: "A creator registers a new project."
method: POST
path: "project.created"
tags: ["project.* events"]
---

# A creator registers a new project.

`POST project.created` (webhook)

### 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](https://docs.subscriby.net/api/v1/reference/projects) 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

- `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` 'project.created', required: The event name, always `project.created` 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.
    - `project` object, required: Snapshot of the new project: `id`, `name`, `handle`, `active`, `team_id` only.
      - `id` string, uuid, required: Project identifier; matches the top-level `project_id`.
      - `name` string, required: Display name shown in the dashboard and on the public landing page.
      - `handle` string, required: URL slug for the public landing page.
      - `active` boolean, required: Always `true` at creation; flips on archive / restore.
      - `team_id` string, uuid, required: Team that owns the project (a personal team for solo creators).

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