
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.
curl --request GET \--url https://api.courier.com/messages \--header 'authorization: Bearer <AUTH_TOKEN>'
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}.
curl --request GET \--url https://api.courier.com/messages/1-5f3d7aa7-e4b8f9ba9a4672ba5d46754c \--header 'authorization: Bearer <AUTH_TOKEN>'
If you would like to retrieve the details provided in the log details timeline, you can use GET /messages/{message_id}/history.
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

Clinical alert and notification systems: how escalation works
A clinical alert is easy to send and hard to close. This is how alerting works inside a hospital: where alerts come from, how routing by role and shift works, and how the acknowledge, timeout, escalate loop is actually built, including what happens when nobody answers.

How to send Slack notifications from your app
Slack is where your customers already work, which makes it a product surface rather than only an internal alerting channel. Posting an approval request or a status change into a customer's own Slack means working in workspaces you don't own, addressing people by email rather than Slack ID, and holding a separate credential for every customer.

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.