Introducing the Lists API: Notify Lists of Users With One API Call
Nate Munger
October 13, 2020
Table of contents
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.
part1part1.part2part1.part2.spart3part1.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
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
Customer Engagement Platform vs CRM: Key Differences Explained
A CRM stores customer data: contacts, purchases, support tickets, and pipeline. It answers "who are our customers?" A customer engagement platform (CEP) orchestrates communication across email, push, SMS, in-app, and chat. It answers "what should we tell them next?" CRMs focus on historical records. CEPs process real-time behavior and trigger messages based on actions. Most teams need both, plus a third layer: notification infrastructure for reliable multi-channel delivery. Courier bridges CEP and infrastructure by combining routing, failover, and delivery tracking with engagement features like preference management, visual templates, and in-app notification centers.
By Kyle Seyler
January 07, 2026
© 2026 Courier. All rights reserved.