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 messages sent via the API to a small audience (fewer than 10 devices), as they are not displayed in the main dashboard by default to avoid clutter.
There are two primary ways to track these API-triggered messages:
1. Use API Messaging Tracing (For Temporary UI Tracking)
This feature allows you to temporarily view all API-triggered messages in your Message History, regardless of the audience size, making it useful for real-time debugging and verification.
- How to enable: Navigate to the Message History section of your project and click the Start API Messaging Tracing button.
- Duration: This tracing mode remains active for approximately one hour and then deactivates automatically. While active, you can see all API sends and their delivery statuses directly in the user interface.
2. Use the Statistics API (For Permanent Data Retrieval)
For a permanent and programmatic way to access delivery data for all API messages, you can use the /getMessageLog method of our Statistics API.
- Functionality: This API endpoint can retrieve detailed, message-level information, including delivery status, for any message, even those not visible in the Message History dashboard.
- Documentation: For more details on how to use this method, please refer to our Statistics API documentation.
Comments
0 comments
Please sign in to leave a comment.