How can I track statistics for transactional messages sent via the API?

You may notice messages labeled as "Transaction" in an individual user's history that do not appear in your main Message History dashboard. This is expected behavior: for load-balancing reasons Pushwoosh does not store a message sent now via the API to an explicit list of fewer than 10 users and fewer than 10 devices. The message is still delivered and still counted in your delivery statistics. Messages scheduled for a future send_date, messages sent to 10 or more users or devices, to a segment or filter, or to all subscribers are stored.

There are two primary ways to track these API-triggered messages:

1. Use API Messaging Tracing (for temporary UI tracking)

This feature temporarily writes such API-triggered messages to your Message History regardless of the audience size, which makes it useful for real-time debugging and verification.

• How to enable: open Campaigns → One-time messages (the Message History view) and click Start API messaging tracing in the upper right corner.
• Duration: tracing turns off automatically after 1 hour. While it is active you can see these API sends and their delivery statuses directly in the interface.
• Scope: tracing is switched on at the account level, so it applies to every application in the account.

2. Use the Statistics API (for programmatic retrieval)

Use the /getMessageLog method of the Statistics API to retrieve message-level records for messages that are not stored. Looking them up by message code returns no events, so filter by recipient instead.

• Request: pass application_code, the recipient's hwid or user_id, date_from and date_to covering the send time, and message_type set to "transactional".
• Response: returns records with timestamp, message code, HWID, User ID, platform, action and status.
• Retention limit: the log is not a permanent archive — data can be downloaded for a maximum of 30 days back from the current time, so poll it regularly if you need a longer history in your own storage.
• Documentation: see our Statistics API documentation.