Operation
Add event note
POST
/events/{id}/notesAdd a staff note to an event, internal by default. Needs the permission to update the event; a restricted note also needs the restricted update permission (403 NOTE_TIER_FORBIDDEN). The note, and every later change to it, is in the event's history.
Path parameters
idstringRequired- Event ID
Headers
Idempotency-KeystringOptional- Makes the write safe to retry. The first request with a key does the work and its response is stored for 24 hours; a repeat with the same key and the same request (method, path, query, X-Ticketlayer-Channel, TL-Version and body) gets that stored status and body back, marked `Idempotent-Replay: true`, without running again. The key is scoped to your organisation and your credential. The same key with a different request is 422 IDEMPOTENCY_KEY_REUSED; a repeat while the first is still running waits for it, then answers 409 IDEMPOTENT_REQUEST_IN_PROGRESS if it has not finished. Only a 2xx is stored: after an error the key is free again. Omit the header and the request behaves as it always has.
Body
Returns
Note added
Errors
- 400
- Bad Request - Invalid input
- 401
- Unauthorized - Authentication required
- 403
- Forbidden - Insufficient permissions
- 404
- Not Found - Resource not found
- 500
- Internal Server Error
Every error names its code and links to it. All error codes
curl -X POST "https://api.ticketlayer.com/v1/events/evt_abc123/notes" \ -H "Authorization: Bearer tlak_..." \ -H "X-Ticketlayer-Org: your-org-slug" \ -H "Content-Type: application/json" \ -d '{ "body": "Comp for the promoter.", "tier": "internal" }'Response 201
{
"note": {
"id": "nte_abc123def456ghi789jk",
"objectType": "order",
"objectId": "ord_abc123xyz789",
"tier": "internal",
"body": "Customer called: wants the seats moved to the aisle.",
"author": {
"kind": "user",
"id": "usr_abc123"
},
"legacyField": null,
"createdAt": "2026-10-02T10:30:00.000Z",
"editedAt": null,
"deletedAt": null,
"redactedAt": null
}
}