Notifications

Mark a notification read

curl -X POST https://api.subscriby.net/v1/me/notifications/$NOTIFICATION_ID/read \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)"

Answers 200 with the entry, read now true. Idempotent: an entry already read keeps its first read_at.

post/v1/me/notifications/{notification}/read

Request

  • Base URL: https://api.subscriby.net
  • URL: https://api.subscriby.net/v1/me/notifications/{notification}/read
  • Auth: HTTP bearer

Path parameters

notificationstring required

The row, resolved by the route binder as the caller's.

Headers

Idempotency-Keystring uuid required

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Response

200 with the row, read.

Example response

{
  "data": {
    "id": "0b1f6e2a-7c3d-4e5f-8a9b-0c1d2e3f4a5b",
    "class": "support",
    "class_label": "Support",
    "title": "Support backlog in Signals",
    "body": "Three members are waiting for an answer.",
    "route": "projects.inbox",
    "url": "https://app.subscriby.net/projects/7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13/inbox",
    "created_at": "2026-09-12T10:05:30Z"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.