project.resource.created
New resource registered under a project.
When this fires
A creator registers a new resource on the project — a Telegram channel, group, supergroup, or manual perk.
Required ability
project-resource:view-any — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "project.resource.created",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"resource": {
"id": "rsr_01HX...",
"type": "channel",
"title": "Research Premium Lounge",
"description": "Weekly drops + live AMAs.",
"chat_id": "-1001234567890"
}
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always project.resource.created for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | string ULID | Project this event belongs to. |
data.resource.id | string ULID | Resource identifier. |
data.resource.type | enum: channel | group | supergroup | manual | Resource flavour. |
data.resource.title | string | Display title. |
data.resource.description | string | null | Optional creator-supplied description. |
data.resource.chat_id | string | null | Telegram chat id; null for manual perks. |
Caveats
- For Telegram-backed resources, expect
project.resource.linkedto follow once the bot is granted admin in the chat. - Manual perks (
type: "manual") carry no chat id and are not linkable; they appear once on creation and once on deletion.
Related events
project.resource.linked— Telegram chat is bound after creation.project.resource.deleted— terminal state for a resource.- Project events overview — back to family overview.
How is this guide?