> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-developer-guide/api-documentation/recipes/monitoring-delivery-results.md). # Monitoring Delivery Results of Your Sends Read the statistics of a send or of a time range, and the per-user result with the error details. This recipe shows how to read how your sends performed: the statistics of a single notification, the statistics of all sends in a time range, and the delivery result of each user with the error details of failures. ## When to Use This recipe fits reporting jobs and support checks, such as a daily summary of sends, or an investigation of why a user did not receive a push. ## Prerequisites * REST API key of the application * The `notificationKey` of the send, returned when the notification was created * For time range queries: start and end dates as epoch timestamps in milliseconds ## Step 1: Read the Statistics of One Notification Pass the `notificationKey` to `getPushStats`. ```bash curl 'https://restapi.netmera.com/rest/3.0/getPushStats?notificationKey=234' \ --header 'X-netmera-api-key: ' ``` The response contains the `status`, for example `FINISHED`, the `startDate` and `endDate` of the send, and a `stats` array with the `sent`, `failed`, and `clicked` counts per platform. **Expected result:** Per-platform counts for the notification. ## Step 2: Read the Statistics of a Time Range To see all sends in a period, pass `start` and `end` instead of a notification key. Both are required and given in milliseconds. ```bash curl 'https://restapi.netmera.com/rest/3.0/getPushStats?start=1796000000000&end=1796600000000' \ --header 'X-netmera-api-key: ' ``` The response contains a `messages` array. Each entry has the `notificationKey`, the `status`, and the `stats` of one send. A send that is still running shows the status `SENDING`. **Expected result:** One entry per notification in the time range. ## Step 3: Read the Result of Each User For user-level results, call `getPushResult` with the `notificationKey`. Add `extId` to narrow the result to one user, or `token` to narrow it to one device. `max` sets the page size and defaults to 10. Without `start` and `end`, the results of the last 2 weeks are returned. ```bash curl 'https://restapi.netmera.com/rest/3.0/getPushResult?notificationKey=234&extId=user_1001&max=10' \ --header 'X-netmera-api-key: ' ``` Each entry in `list` contains the `platform`, the `status` (`SUCCESS` or `FAILED`), the `timeStamp`, and the title and text of the message. A failed entry also carries an `errorCode` and an `errorMsg`, for example `INVALID_TOKEN`. When more results exist, the response contains a `nextPage` URL. Send a request to that URL, with the same `X-netmera-api-key` header, to read the next page. **Expected result:** One entry per device of the user, with a status. ## Step 4: Check Email and SMS Sends When you pass the notification key of an earlier email or SMS send to `getPushResult`, the response returns the success and failure details of each individual email or SMS. ## Verification Checklist * Time range queries use epoch timestamps in milliseconds for both `start` and `end` * The `status` is `FINISHED` before the counts are used as final numbers * `getPushResult` is called with the `notificationKey` of the send * Pagination follows the `nextPage` URL until it is no longer returned * Failed entries are investigated with their `errorCode` and `errorMsg` ## Related Pages For all parameters and sample responses, see the Push Stats and Get Push Result sections of the [Notifications](/netmera-developer-guide/api-documentation/rest-api/notifications.md) page in the REST API documentation. For a first send and its statistics, see [Sending a Push Campaign to a Tagged Audience](/netmera-developer-guide/api-documentation/recipes/sending-push-to-tagged-audience.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://user.netmera.com/netmera-developer-guide/api-documentation/recipes/monitoring-delivery-results.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.