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 We Investigate Support Tickets at Courier
Courier's support team resolves complex issues 4X faster using parallel investigation. Here's how it works: when a ticket comes in, an AI agent starts exploring the codebase while the support engineer examines actual customer data. The agent traces code paths and searches past investigations. The human reads event logs and forms hypotheses based on real state. Running both simultaneously catches mismatches fast—the agent sees what could cause a problem, the human sees what actually happened. This post breaks down the workflow, tools, and documentation structure that makes it repeatable.
By Thomas Schiavone
December 18, 2025
Top 20 Notification Examples That Actually Drive Engagement
Explore 20 stellar notification examples from industry leaders like Rippling, Slack, FedEx, Crocs, Miro, Trustpilot, OpenTable, and BambooHR that actually drive engagement. From payday celebrations to healthcare reminders, these patterns showcase what makes notifications effective across email, SMS, push, and in-app channels. Courier's enterprise platform enables intelligent routing, multi-channel orchestration, and universal inbox integration to implement these proven patterns at scale.
By Kyle Seyler
September 25, 2025
Video Guide: Courier MCP + AI Coding (Cursor)
Building notifications into your app just got dramatically easier. Courier's new MCP server brings AI-powered notification assistance directly to your IDE, so you can integrate, test, and manage notifications without ever leaving your workspace. Model Context Protocol servers give AI agents deterministic functionality instead of guessing. Connect your AI assistant directly to Courier's platform, get smart installation guidance, send messages with natural language, and manage users safely—all through Cursor, Claude Code, VS Code, and more.
By Kyle Seyler
September 04, 2025
© 2025 Courier. All rights reserved.