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:
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.
You can retrieve a pageable list of log messages using GET /messages.
Copied!
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!
If you would like to retrieve the details provided in the log details timeline, you can use GET /messages/{message_id}/history.
Copied!
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

The $5.9 Billion Rebuild: Why Healthcare Is Replacing Its Notification Infrastructure
The clinical alert and notification market will reach $5.9 billion by 2032, growing at 12.3% annually. That number represents hardware, software, and services combined. It also represents healthcare's admission that pagers and overhead speakers aren't enough anymore. Healthcare organizations are rebuilding how critical information moves through their systems. Regulatory pressure, workforce shortages, and value-based care economics are forcing the investment. The software layer is where outcomes are won or lost.
By Kyle Seyler
February 02, 2026

Vibe Coding Notifications: How to Use Courier with Cursor or Claude Code
Courier's MCP server lets AI coding tools like Cursor and Claude Code interact directly with your notification infrastructure. Unlike Knock and Novu's MCP servers that focus on API operations, Courier's includes embedded installation guides for Node, Python, Flutter, React, and other platforms. When you prompt "add Courier to my app," your AI assistant pulls accurate setup instructions rather than relying on outdated training data. OneSignal's MCP is community-maintained, not official. Courier supports 50+ providers, native Slack/Teams integration, drop-in inbox and preference components, and a free tier of 10,000 notifications/month. Configure in Cursor with "url": "https://mcp.courier.com" and "headers": { "api_key": "YOUR_KEY" }.
By Kyle Seyler
January 22, 2026

The Complete Guide to B2B Customer Engagement
Courier provides the notification infrastructure layer for B2B customer engagement, routing messages across email, SMS, push, in-app, Slack, and Teams based on user preferences and product events. Unlike building notification systems in-house—which takes months of engineering time for features like multi-channel routing, preference management, and delivery tracking—Courier handles this infrastructure so product teams can focus on engagement strategy. B2B customer engagement requires multiple layers: notification infrastructure (Courier), customer data platforms (Segment), product analytics (Mixpanel/Amplitude), and channel-specific tools. Companies with strong engagement programs see 15-25% churn reduction. The key is connecting product events to customer communication at the right moment through the right channel, handling complexity like multiple users per account with different notification needs across work channels.
By Kyle Seyler
January 20, 2026
© 2026 Courier. All rights reserved.
curl --request GET \--url https://api.courier.com/messages \--header 'authorization: Bearer <AUTH_TOKEN>'
curl --request GET \--url https://api.courier.com/messages/1-5f3d7aa7-e4b8f9ba9a4672ba5d46754c \--header 'authorization: Bearer <AUTH_TOKEN>'
curl --request GET \--url https://api.courier.com/messages/1-5f3d7aa7-e4b8f9ba9a4672ba5d46754c/history \--header 'authorization: Bearer <AUTH_TOKEN>'