A new release of Courier's Flutter SDK is live!

The new release contains the following updates:

• All thread and event updates from recent iOS and Android changes

• Updates docs

• Support for custom error message in CourierInbox and CourierPreferences

A new release of Courier's React Native SDK is live!

The new release contains the following updates:

• Improved threading stability on iOS and Android

• New docs to make it easier to support Expo apps

A new release of Courier's Android SDK is live!

This new release contains the following updates:

• A fully rebuilt inbox datastore

  • Inbox messages and events are handled similarly to iOS to prevent data collisions

• Simplified inbox listener events

  • New onMessageEvent callback allows you to listen to a specific event to build any UI you want

• Additional unit and integration tests to cover these new features

Due to our Google Play account being locked by Google, you have to pull the package to install this example app.

A new release of Courier's iOS SDK is live!

This new release contains the following updates:

• Better socket connection handling when switching from foreground to background

• Significant threading improvements.

  • All functionality using Courier.shared.. now executes on a specific Courier only thread called CourierActor

• A fully rebuilt inbox datastore

  • Inbox messages and events are managed entirely with the CourierActor to ensure reliability and data precision

• Simplified inbox listener events

  • New onMessageEvent callback allows you to listen to a specific event to build any UI you want

• Additional unit and integrations test to cover all of these new features

A live test build can be found here.

The new histogram for message logs gives users insights into their notification performance.

With Courier's new histogram feature for message logs, users can have high-level insights for their daily notification performance. The table graph can be queried for specific periods and break down message stats for each day. The histogram can also be highlighted for more specific date ranges.

The assets page has a new look. Message and automation templates can be found in separate tabs within the asset manager. Two new columns have also been added to the asset manager, giving users insights on their notification performance within a specified time.

AWS SES users can now benefit from IAM role authentication for their AWS SES integration with Courier.

This method reduces the risk of credential leakage and simplifies credential management by using temporary, automatically rotated credentials. If you already use IAM Roles in your AWS infrastructure, this update helps you align your email authentication with your existing security practices.

Read more here.

By default, Email and Inbox channels that make up the same notification template synced event statuses. This meant that if a notification was sent with an in-app inbox and email channel, opening an email will mark the in-app inbox notification as read. Courier Inbox and email events can now be un-synced when sent simultaneously.

Apple recently announced an APNS Security Update, requiring updated server certificates for push notifications starting March 29, 2025. If you rely on Apple Push Notification Service (APNS) for delivering notifications to iOS devices, you may be wondering what actions, if any, are needed to ensure uninterrupted service.

We’re excited to confirm that Courier customers are unaffected by this update. Notifications sent via APNS with P8 keys or P12 certificates work seamlessly, and no immediate changes are required.

Fixed a bug where refreshing a page or clicking an external link to the changelog would add a trailing slash. Basically added /changelog/ to every link… 🤦

You can now control when your notifications are sent with our Delivery Window feature! Set specific time ranges for delivery, handle multiple timezones seamlessly, and ensure messages are sent exactly when you want.

It's not time to debug your automation workflows. You can run test events, view data diff between nodes, quickly validate nodes at-a-glance. We also added a GET Profile node top help you dynamically fetch any Courier profile.

The Message Tags as a Template Setting feature enables users to tag their messages directly from the Notification Template. When messages are sent, these tags are parsed and added to the metadata tags field. This allows messages to be filtered in the inbox or through the Messages API using the specified tags.

The webhook payload for outbound messages included an empty tags object when tags were specified in the send request via metadata.tags. This issue was resolved, and the tags object was ensured to reflect the provided metadata.tags accurately.

Courier's POST `/profiles/:user_id` (`profiles.create()`) endpoint would accept an empty profile object, return a `{SUCCESS: true}` but not create the profile. This endpoint was updated to mimic the other endpoints and allow an empty profile to create a user.

The Message Tags as a Template Setting feature enables users to tag their messages directly from the Notification Template. When messages are sent, these tags are parsed and added to the metadata tags field. This allows messages to be filtered in the inbox or through the Messages API using the specified tags. The feature is accessible under a feature flag, which requires activation by contacting courier support or the account team.

Courier's POST /profiles/:user_id (profiles.create()) endpoint would accept an empty profile object, return a {SUCCESS: true} but not create the profile. Other endpoints and methods (like .identify() would allow for creating a profile with an empty object. This endpoint was updated to mimic the other endpoints and allow an empty profile to create a user.

The webhook payload for outbound messages included an empty tags object when tags were specified in the send request via metadata.tags. This occurred regardless of the presence of tag data, as demonstrated by an empty tags: {} array in the payload. This issue was resolved, and the tags object was ensured to reflect the provided metadata.tags accurately.

Customers experienced a 404 error when using the Send Again feature on undeliverable notifications for ad-hoc sends that included a fan-out (lists, tenants, array of profiles, audiences). The endpoint was rewritten to address this problem and now successfully supports re-queuing ad-hoc list messages.

Customers experienced a 404 error when using the Send Again feature on undeliverable notifications for ad-hoc sends that included a fan-out (lists, tenants, array of profiles, audiences). The Send Again feature would work for the full original message but would fan out and re-send to all recipients. The endpoint was rewritten to address this problem and now successfully supports re-queuing ad-hoc list messages.

Messages sent with a delay were initially not visible in the logs UI or through the API, even though a request ID was provided. The visibility problem was resolved with recent changes that created first-class request entities and stored them alongside messages, allowing delayed messages to appear correctly in the logs and API responses.

We added archive APIs to our iOS, Android, and React Native SDKs, allowing you to build a swipe left to remove from the Courier Inbox. Enable your users to declutter their inboxes and keep only the notifications they want to save for later.

Fixed miscellaneous errors with the switch node, including access to deeply nested data. This issue has been fixed.

Digesting a Send API feature allows business and enterprise customers to aggregate frequent transactional messages into scheduled digests without requiring code changes. Admins in Courier link notification templates select a Linked Digest Template and set schedules for sending aggregated messages by configuring digests in the Preferences Editor.

The tenants page in the Database tab did not persist changes made to the JSON fields, although the changes were saved and could be retrieved via the API and used in notifications. This has been fixed.

Implemented a feature to handle ThrottleException errors more effectively using SES's sendRawEmail function. Previously, a 400 status with ThrottleException would not trigger retries, potentially disrupting email delivery processes. With the new update, such errors now throw a retryable provider error to ensure more robust and resilient email sending

We've updated our notification pipeline to catch ThrottleException thrown by AWS SES in the case the SES account has reached its thresholds. This is now a retryable error, and notifications will automatically be retried with an exponential backoff.

Fixed a bug where invoke automation steps failed when null values were found in optional fields.

Courier Inbox websockets experienced issues with users with 100+ active connections. Toasts and live messages were not delivered to those users. This has been resolved.

For some customers, analytics sparklines were not appearing. For the customers affected, they should now start seeing usage analytics for the template on their Asset Page