---
title: "Message history"
method: POST
path: "/notifications/{message_id}/history"
---

# Message history

`POST /notifications/{message_id}/history`

View which subscriptions received a particular message

## Path parameters

- `message_id` string, required

## Headers

- `Authorization` string, required

## Request body

- object
  - `app_id` string, required — Your OneSignal App ID in UUID v4 format. See [Keys & IDs](/docs/en/keys-and-ids).
  - `events` string, required — Specifies the type of event to retrieve. `sent` — retrieves all subscriptions sent the specified message. Note: sent events are not recorded for messages targeting fewer than 1,000 recipients. `clicked` — retrieves all subscriptions that interacted with the message. Note: There isn't a recipient count threshold for tracking clicked event.
  - `email` string — The email address in which to deliver the report.

## Response `202`

Accepted. The history-export job was enqueued. The export is delivered asynchronously to the configured S3 destination.

- object
  - `success` boolean
  - `destination_url` string

## Other responses

- `400` — 400
- `429` — Rate limit exceeded. Wait the number of seconds in the `Retry-After` header before retrying.
- `503` — Service temporarily unavailable. Retry after a short backoff. The body may be empty or non-JSON in some failure modes.

---

[API](https://skmtc.net/onesignal/apis/api-onesignal-com.md) · [All operations](https://skmtc.net/onesignal/apis/api-onesignal-com/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/onesignal/api-onesignal-com/revisions/0fc223f7e338/schema)