---
title: "A manual perk is registered under a project."
method: POST
path: "project.resource.created"
tags: ["project.* events"]
---

# A manual perk is registered under a project.

`POST project.resource.created` (webhook)

### When this fires

A creator registers a manual perk on the project, from the dashboard's resource editor, `POST /v1/projects/{project}/resources` or the `create_resource` tool. A place a connector gates never arrives here: the connector links it and announces `project.resource.linked` instead.

The resource `description` is **not** included in the payload. Fetch it with [the resource endpoint](https://docs.subscriby.net/api/v1/reference/resources) if you need it.

### Caveats

- `project.resource.linked` is not a follow-up to this event; it creates its own resource row and carries a different `resource_id`.
- A manual perk is bound to no place and is not linkable; it appears once on creation and once on deletion.

### Related events

- `project.resource.linked`: a place a connector gates becomes a resource.
- `project.resource.deleted`: terminal state for a resource.

## 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.resource.created', required: The event name, always `project.resource.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.
    - `resource` object, required: The new resource: `id`, `title`, `kind`, `connector`, `space`, `active` only.
      - `id` string, uuid, required: Resource identifier.
      - `title` string, required: Display title.
      - `kind` string, required: Always `manual` on this event. A connector's kind (`telegram:channel`) appears via `project.resource.linked`.
      - `connector` string, nullable, required: Always `null` here: a manual perk lives on no connector.
      - `space` object, nullable, required: Always `null` here: a manual perk is bound to no place.
      - `active` boolean, required: Active flag at creation time.

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