Blog
COURIERPRODUCT NEWS

Introducing the Lists API: Notify Lists of Users With One API Call

Nate Munger

October 13, 2020

List API hero

Table of contents

Read more

Companies today send user notifications across a growing number of platforms and channels. To help you send the right notification on the right channel at the right time, Courier lets you define your user preferences and store them on a recipient profile via our Profiles API.

But there’s another challenge: many times there are groups of users you want to message with the same notification triggered by the same event.

In the past, this meant tens or sometimes thousandsof API calls triggering the same notification over and over. But now, with the release of Courier’s Lists API, you’re able to create lists, subscribe recipient profiles to them, and notify every user on the list with a single Send API call.

Courier handles the message fanout – following user preferences and your channel priorities – to deliver across email, SMS, mobile push, messaging apps, and more.

Copied!

curl --request POST \
--url https://api.courier.com/send/list \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '{"list":"webapp.new_feature.alpha_users","event":"alpha_access_granted"}'

With the Lists API, you can easily do things like:

  • Reach every user in a shared workspace.
  • Notify all users who follow a specific project.
  • Message users who opt in to select notifications.

Wildcard Sends: Notify subscribed users, across multiple lists, with one API call

The Lists API accepts List IDs with up to four parts. Giving you plenty of flexibility to create lists for almost any use case.

  • part1
  • part1.part2
  • part1.part2.spart3
  • part1.part2.part3.part4

Following this basic pattern when defining List IDs will enable wildcard sending. This means you can send to multiple list parts within a related pattern using a single API call.

Copied!

curl --request POST \
--url https://api.courier.com/send/list \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '{"pattern":"webapp.new_feature.*","event":"new_feature_access_granted","brand":"W50NC77P524K14M5300PGPEK4JMJ","data":"{\"name\": \"Jane Doe\",\"age\": 27}"}'

When sending to a Pattern that matches multiple Lists, Courier will send only one notification to any user with multiple matching subscriptions.

Get started with the Lists API

For more details on how to create and send to lists, check out the Lists API reference doc. You can read more about how to name your lists and use wildcards in our Lists API help article.

Read more

Courier Live: First Look at Notifying Multiple Recipients using Lists

Similar resources

customer engagement and notification infrastructure image
Notifications LandscapeCourierProduct Management

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

Top Customer Engagement Platforms for SaaS in 2026
Notifications LandscapeCourier

Top 8 Customer Engagement Platforms for Product-Led SaaS in 2026

Comparing Courier, Iterable, OneSignal, Braze, Customer.io, Knock, Novu, and SuprSend across orchestration, developer experience, and infrastructure primitives for product-led SaaS.

By Kyle Seyler

February 19, 2026

transactional emails, transactional push notifications
Notifications LandscapeCourierProduct Management

What are transactional notifications? Transactional email examples, transactional push, and more.

Transactional notifications are automated messages triggered by user actions or system events, like password resets, order confirmations, and payment alerts. Unlike marketing messages, they require no opt-in and have legal protections under CAN-SPAM. This guide covers what transactional notifications are, how they work across email, SMS, and push channels, real-world examples for each, and how to stay compliant. Whether you're building your first notification system or auditing an existing one, this breakdown will help you understand what belongs in each category and how to route messages correctly.

By Kyle Seyler

February 17, 2026

Multichannel Notifications Platform for SaaS

Products

Platform

Integrations

Customers

Blog

API Status

Subprocessors


© 2026 Courier. All rights reserved.