Skip to main content

Prerequisites

Setup

1

Create an Airship auth token

In Airship, open your project at go.airship.com and create a bearer token. The base URL is your project’s region endpoint.
2

Configure in Courier

Open the in Courier, enter your auth token and base URL, 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. Airship addresses the recipient by audience and device types, both under airship on the profile. Store them once with , which merges into the profile and creates it if it does not exist:
Then send to user_id and Courier resolves the address. For a one-off with no stored profile, pass it inline instead: "to": { "airship": { "audience": { "named_user": "user_123" }, "device_types": ["ios"] } }.

Send by user id

The call in every language, and the rest of the profile object.

Send to a recipient

Courier reads airship off the saved profile, so preferences apply and the value can change without touching this code.

Overrides

covers the two levels and which one wins. lists the fields every push provider takes. A provider override changes what Courier sends to Airship’s API. For example, use basic auth on one send request:
Overrides are deep-merged into the request. Fields you set replace their counterparts, and everything you leave out is still sent. The full field list is in Airship’s API docs.

Tracking events

Courier puts the tracking URL in the global_attributes data bag. See for details.

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.