Getting the Most out of Courier Logs
Aydrian Howard
August 26, 2020
Table of contents
During our August 19th Courier Live, Tony Nguyen from our engineering team joined me to talk about my favorite Courier feature, the logs. We presented a high level overview of the logs and dove into the details of each timeline event in the Courier Application. We then covered how you could retrieve the same information using the Messages API.
Check out the video below to watch us:
- Explain the basics of the Courier Logs
- Walk through the lifecycle of a notification
- Explore the notification statuses
- Use the Messages API to retrieve message events and history
Retrieving Log Details Programmatically
While Courier provides a great graphical experience for viewing their logs, sometimes you need to be able to grab that information as part of a backend process. This can be done using the Messages API.
Listing Messages
You can retrieve a pageable list of log messages using GET /messages.
Copied!
curl --request GET \--url https://api.courier.com/messages \--header 'authorization: Bearer <AUTH_TOKEN>'
Fetching a single Message
Once you have a messageId, either from the call above or the response of a send call, you can use it to get more details using GET /messages/{message_id}.
Copied!
curl --request GET \--url https://api.courier.com/messages/1-5f3d7aa7-e4b8f9ba9a4672ba5d46754c \--header 'authorization: Bearer <AUTH_TOKEN>'
Getting Message History
If you would like to retrieve the details provided in the log details timeline, you can use GET /messages/{message_id}/history.
Copied!
curl --request GET \--url https://api.courier.com/messages/1-5f3d7aa7-e4b8f9ba9a4672ba5d46754c/history \--header 'authorization: Bearer <AUTH_TOKEN>'
You can learn more about the Courier API from the Courier API Reference Documentation.
Is there something you’d like to see us do using Courier? Let us know and it might be the subject of our next Courier Live. We stream a new Courier Live every Wednesday at noon Pacific. Follow us on Twitch to be notified when we go live.
-Aydrian
Similar resources
How Product Teams Build, Test and Ship Multichannel Notifications in Design Studio
Product teams need to build, test, and ship notifications across multiple channels without filing an engineering ticket every time. Courier's Design Studio is the workspace for that: a template builder, visual channel routing, omnichannel testing, and publishing in one place. This post walks through the traditional template designer paradigm, how it splits effort across too many tools, and outlines a path for product and growth teams to ship transactional, product, and marketing notifications from a single workspace.
By Kyle Seyler
March 12, 2026
EU Data Residency for Notifications: What Engineering Teams Need to Know
Courier supports EU data residency through a dedicated datacenter in AWS EU-West-1 (Ireland), with full API feature parity, same-workspace dual-region access, built-in GDPR deletion endpoints, and localization support for multilingual notifications. Engineering teams can switch to EU hosting by changing a single base URL with no workspace migration or downtime required.
By Kyle Seyler
March 09, 2026
Customer Engagement Platforms Are Splintered. Message Orchestration Is the Fix
Customer engagement platforms are splintered. Some are built for campaigns, others for support automation, and others treat messaging as a transactional delivery problem. The result is collisions, blind spots, and message fatigue. The highest-leverage fix is solving the lifecycle-to-product and transactional vector with a message orchestration layer: one system that routes, suppresses, prioritizes, and observes messages across channels. Think air traffic control for user communications.
By Kyle Seyler
March 03, 2026
© 2026 Courier. All rights reserved.