Integrations/Pusher Beams
Pusher Beams logo

Pusher Beams + Courier

Turn Pusher Beams push into a complete mobile notification system

Design and automate every message with Courier. Keep Pusher Beams for push delivery, then add SMS and an in-app inbox from one API.

Overview

What Pusher Beams is

Pusher Beams is a hosted push notification service that delivers push to iOS, Android, and web across multiple delivery channels.

Courier sits in front of it, manages device tokens for you, and adds an in-app inbox and SMS, so you get a complete mobile messaging stack from one API.

You need a Courier account and your own Pusher Beams instance with its Instance ID and Secret Key.

Why Courier

What you get with Pusher Beams + Courier

Use cases

What teams build with it

Send push across iOS, Android, and web without managing device tokens yourself
Pair push with an in-app inbox so users can revisit notifications inside your app
Reach users with SMS alongside push for complete mobile coverage from one send
Automate onboarding and re-engagement journeys across push, in-app, and SMS
Let non-technical teammates design and edit push without a deploy

Setup

Connect it in minutes

An admin adds Pusher Beams once on the Integrations page in Courier. Once connected, Courier manages tokens and your team can send push, add an in-app inbox, and layer in SMS.

1
Add Pusher Beams in Courier
Open Integrations, select Pusher Beams, and enter your Instance ID and Secret Key.
2
Store device tokens
Send your users' push tokens to Courier; it manages registration and expiry across platforms.
3
Send from your app
Call the Send API with a recipient and template. Courier delivers push through Pusher Beams, plus any other channels you add.

FAQ

Frequently asked questions

Can I use Pusher Beams with Courier?

Yes. Pusher Beams is a push provider you configure in Courier, then trigger through the Send API. Beams handles delivery to devices while Courier owns the content and routing across your channels.

Do I still need my own Pusher Beams account?

Yes. Courier connects to your existing Beams instance using its instance ID and secret key. Beams remains the account that owns your instance and manages device registrations; Courier orchestrates what gets sent and when.

What do I need to connect Pusher Beams to Courier?

A Beams account with an instance already configured, plus that instance's instance ID and secret key. Enter both on Courier's Pusher Beams integration page and click Save.

How do I target recipients on Pusher Beams through Courier?

Two ways: interests or users. Set an interests array to reach subscriber groups, or a userIds array to reach specific authenticated users. Courier passes your chosen targeting to the Beams API on each send.

Which platforms can Pusher Beams reach through Courier?

You pick delivery modes: web, apns for iOS, and fcm for Android. At least one mode is required on every send, and you can combine them to reach multiple platforms in one notification.

Can I customize the Pusher Beams payload or credentials per send?

Yes. Use the override object to modify the request body sent to Beams, such as the FCM notification title and body. You can also override the instanceId or secretKey at send time.

Is Courier a replacement for Pusher Beams?

No. Pusher Beams still delivers the push to devices. Courier adds one Send API, content design, Journeys, and other channels like email, SMS, and Courier Inbox on top of it.

More

Related integrations