Skip to main content

Prerequisites

Setup

Open the in Courier, enter your API key, then click “Save.”

Profile requirements

Device tokens live on the user profile rather than on the send, so one profile can hold tokens for several devices and every push provider reads them from the same place. covers the model. NowPush needs no profile data. If your notification template includes device_type, message_type, url or apiKey, those values replace the configuration.

Overrides

covers the two levels and which one wins. lists the fields every push provider takes. A provider override changes the request body Courier sends to NowPush, or swaps the API key and URL.

Body overrides

This example sets the device type and the message type:

Config overrides

Swap the API key or URL at send time with a config override:

Provider details

Courier recommends routing to the channel. Naming this key in routing.channels instead is supported, and sends through just this provider.

Send to a specific provider

When that is worth doing, and what you give up: failover, channel priority, and providers you add later.