Overview
All webhook events follow a consistent payload structure. This document describes the standard format used across all event types.Standard Event Structure
{
"id": "evt_01J9ABCDEF",
"type": "note.created",
"createdAt": "2025-09-05T07:12:34Z",
"data": {
"resourceType": "Note",
"resourceId": "1Lvbn2EQKmQvV",
"resource": {
"title": "Meeting Note"
}
}
}Field Descriptions
Top-Level Fields
Unique identifier for this webhook event. Use this for idempotency and deduplication.
Event type identifier (e.g.,
note.created, note.paragraph.updated).ISO-8601 timestamp when the event occurred. Use this for event ordering.
Event-specific data containing resource information.
Data Object Fields
The type of resource that triggered the event. Examples:
Note, NoteSummary, Paragraph.Unique identifier for the specific resource instance. Use this for quick routing and idempotency.
The actual resource data. Structure depends on the resource type and follows our standard schemas.
Event Types
Event types identify the specific action that occurred. Here are some examples:Resource Type Mapping
| Event Type | Resource Type | Schema Reference |
|---|---|---|
note.* | Note | Note Schema |
note_document.* | NoteDocument | NoteDocument Events |
folder.* | FolderNoteRelation | FolderNote Events |