Skip to main content
Release notes are authored per app and per version. Once published, the SDK shows a note to a device only when the note’s version is above the version the device originally installed and at or below the version it runs now — so an upgrade reveals the notes it skipped past, and a fresh install sees nothing.

Authentication

These endpoints accept either a dashboard session cookie or a server API key sent as Authorization: Bearer <key>.
A note belonging to another organization returns 404, never 403 — you cannot tell “not yours” from “not there”.

The release note object


List release notes

Paginated, sorted by creation date descending (authoring order, not version order). Query parameters Response

Get a release note

Response200 OK — the release note object.

Create a release note

Request body
Response201 Created — the release note object. Errors

Update a release note

All fields are optional. Publish state is not settable here — use the publish and unpublish routes so publishedAt stays consistent. Request body
Response200 OK — the updated release note. Errors

Delete a release note

Also removes its view records. Response204 No Content

Publish and unpublish

Both are idempotent and return the release note object with 200 OK. Unpublishing clears publishedAt; seen-state is kept, so a note that is unpublished and republished is not re-shown to devices that already read it.

See also