Returns activity records for the messages sent to your contacts over the period you specify. Each record carries a status — DELIVERED, UNDELIVERED, READ, CLICKED, UNSUBSCRIBED, SUBSCRIPTION_CHANGED, or SPAM — the time it happened, and the message and contact it belongs to. For UNDELIVERED, the reason is returned as well.
Use it to bring message statuses, contact actions, and delivery failures into your own system. Read more...
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
NoteThe method is enabled on request — contact support to activate it for your account. Activation can take a few hours. Activity data starts accumulating from the moment the feature is enabled and is stored for 90 days.
NoteUse this endpoint with the
messageTagand/oractivityStatusto check whether a specific transactional message has already been sent to a contact within a given period — for example, before sending a follow-up so you don't duplicate it. If activity for the message tag and status you're checking is already present in the response, skip the send.If you sent the message through Send prepared message with your own
externalRequestId, the response returns that identifier. Matching on it identifies an individual send precisely, without relying on the message tag and status.
TimingActivity can appear in the response a few minutes after the message is sent, so a check made immediately before a send may not see the previous one yet. Get contact's message history reflects a send right away — use it when the check has to be real-time.
Note
dateFromanddateTovalues without a time part mean midnight UTC of that date. To include activity from the current day, specify the time in ISO 8601 format — for example,dateTo=2026-05-29T10:59:59.