DeluxHostAPI Reference
Notifications

Mark all notifications as read

POST
/v1/notifications/read-all

Authorization

apiToken notifications:write
headerAuthorizationBearer <token>

A personal API token: Authorization: Bearer dh_live_…. See Authentication for scopes.

Scope: notifications:write

Response Body

Operation completed or accepted; asynchronous actions may still be running.

application/json
  1. response
ok*boolean
curl -X POST 'https://api.deluxhost.net/v1/notifications/read-all' \  -H "Authorization: Bearer $DELUXHOST_TOKEN"
Example Response
{  "ok": true}

Dismiss a notification DELETE

List notifications GET

One ordered stream of the things that already reach the dashboard bell: a service provisioned or suspended, an invoice raised, a charge that failed. **This is what to poll** instead of diffing `/v1/services` and `/v1/invoices` against your own copy. Two cursors, and they walk opposite ways: - `before` — page back through history, newest first. - `after` — everything since id N, **oldest first**. That ordering is the point: newest-first, a client that missed more than `limit` rows would advance its cursor past what it never read. `nextCursor` is always passed back in the same parameter you used. Rows can be deleted (the dashboard bell dismisses them), so ids in the feed can have gaps. Read-only: nothing here marks a notification read — `read` is the dashboard's state.