Skip to main content

List send history

GET 
/api/partner-gateway/v1/messages/history

Returns a paginated list of sent messages for the given channel and date range, allowing you to browse your complete sending history with flexible filtering. Use this endpoint when you need to review past sends, audit delivery performance over a time window, or build dashboards and reports on message delivery rates. The channel parameter is required and restricts results to a single messaging channel (SMS, RCS, or WHATSAPP). To retrieve history across multiple channels, make separate requests for each channel. The from and to parameters define the send-date range (inclusive on both ends) and are required. Accepted formats: a date alone (2025-01-15, meaning the whole day in UTC: 00:00:00Z as from, 23:59:59Z as to), a date-time without offset (2025-01-15T10:30:00, read as UTC), or a full ISO-8601 date-time with offset (2025-01-15T00:00:00+01:00 or 2025-06-15T23:59:59Z). Remember to percent-encode a + sign in the offset as %2B: an unencoded + is decoded as a space. A value in none of these formats, or a from later than to, is answered with 400 and a message naming the parameter and the accepted formats. The optional status parameter lets you filter by a specific delivery status: ACCEPTED, REJECTED, DELIVERED, EXPIRED, DELETED, UNDELIVERABLE, ERROR, DISABLED, UNSUPPORTED, CONVERSATION_CLOSED or UNKNOWN. Which ones can appear depends on the channel — see the Delivery Statuses table in the API overview. Omit this parameter to return messages in all statuses. Pagination is controlled by the page and limit parameters. Pages are 0-based (the first page is page=0). The default page size is 20 if limit is not specified. To iterate through all results, increment the page parameter until the response returns fewer items than the requested limit, which indicates you have reached the last page. The response is a JSON array of DeliveryStatusResponse objects, which may be empty if no messages match the given filters. For large date ranges with many messages, consider using the export endpoint (POST /partner-gateway/v1/messages/history/export) to generate a downloadable CSV file instead of paginating through thousands of results. Error responses: 400 for a missing or malformed channel, from or to; 500 indicates an unexpected server-side error; retry after a short delay.

Request​

Responses​

List of sent messages (may be empty)

Last updated on