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 messages sent via the API with a devices array containing fewer than 10 devices. They are still delivered and still counted in your delivery statistics. (Scheduled sends and sends targeted with users, filter, conditions or as a broadcast are always recorded.)

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

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

This feature temporarily writes all 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 all 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)

For programmatic access to delivery data for API messages, use the /getMessageLog method of the Statistics API.

• Functionality: returns message-level records (timestamp, message code, HWID, User ID, platform, action and status) including for messages that are not visible in the Message History dashboard.
• 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.