Skip to main content
GET
Retrieve a push notification delivery trace

Endpoints

  • GET /push/notifications
  • GET /push/notifications/:id
Delivery records cover direct sends, automations, campaigns, and one-device tests. Filter by push app, platform, environment, or status. A detail response includes the provider message ID and chronological provider/client events, including the reporting device and provider name. Use this trace together with push device diagnostics. A provider send event can still be followed by a stale-token failure, OS suppression, foreground-handler behavior, or missing client instrumentation.

Authorizations

Authorization
string
header
required

Integration key for backend workloads, or a scoped personal key (sr_user_) for account discovery and supported project operations. MCP accepts only personal keys.

Headers

X-Sendrealm-Project-Id
string<uuid>

Explicit project context. Required for personal-key project resource calls; integration keys retain their configured default. MCP clients supply project_id in each tool call instead.

Path Parameters

id
string<uuid>
required

Response

Push notification trace returned

status
integer
required

HTTP response status code

data
object
required