https://demo.notifuse.com/api/annotations.create Creates a manual annotation. Requires the web_analytics write permission.
source is always stored as manual and source_id is always empty: only the platform writes automatic rows, so there is no way to attach a caller-supplied key to one. This endpoint is therefore not idempotent — a retried call (a CI job re-running a deploy marker, for instance) writes a second annotation. De-duplicate on the caller's side, or delete the extra row.
Omitted color and timezone are filled in server-side: the default colour, and the workspace timezone falling back to UTC.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your API key.
Body application/json
The moment to mark, as an RFC3339 instant.
IANA timezone the moment was entered in, kept for display. Defaults to the workspace timezone, then to UTC.
Only manual is accepted. Sending broadcast is rejected rather than quietly downgraded: it would be claiming the slot of an automatic row.
Response
201 Annotation created object
Show 10 child attributes Hide 10 child attributes
Server-generated identifier (a UUID with its dashes removed).
The moment the annotation marks, as a real instant.
IANA timezone the moment was entered in. This is display intent only — annotated_at already fixes the instant, and filtering never uses this field. It is what lets "9am in Tokyo" render back as 9am instead of the reader's local equivalent.
Counted in characters, not bytes.
Optional longer note. Counted in characters, not bytes.
Six-digit hex colour used for the marker on the charts.
Who wrote the row. manual is anything typed by an operator or posted to this API; broadcast rows are written automatically when a broadcast starts sending. There is deliberately no API source — see the note on annotations.create.
The entity that caused an automatic annotation (a broadcast id today). Always absent on manual rows, and never settable through the API. An annotation outlives the entity it points at: deleting a broadcast leaves its annotation, because the send did happen.
400 Bad request - unparseable body, validation failed, or the instance runs in demo mode, where every mutating endpoint is closed. object
Error message
401 Unauthorized - invalid or missing authentication token object
Error message
403 Forbidden - missing required permission object
Error message
500 Internal server error object
Error message