Audiences
AuthTokens
Brands
Inbound
Lists
Messages
Notifications
Profiles
Tenants
User Preferences
User Tenants
Get a Job
Get a bulk job
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
A unique identifier representing the bulk job
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
A unique identifier representing the bulk job
Response
A unique identifier that represents the brand that should be used for rendering the notification.
JSON that includes any data you want to pass to a message template. The data will populate the corresponding template variables.
JSON that is merged into the request sent by Courier to the provider to override properties or to gain access to features in the provider API that are not natively supported by Courier.
Describes the content of the message in a way that will work for email, push, chat, or any channel.
The id of the notification template to be rendered and sent to the recipient(s). This field or the content field must be supplied.
An arbitrary object that includes any data you want to pass to the message. The data will populate the corresponding template or elements variables.
"Define run-time configuration for one or more channels. If you don't specify channels, the default configuration for each channel will be used. Valid ChannelId's are: email, sms, push, inbox, direct_message, banner, and webhook."
Context to load with this recipient. Will override any context set on message.context.
An id of a tenant, see tenants api docs. Will load brand, default preferences and any other base context data associated with this tenant.
Metadata such as utm tracking attached with the notification through this channel.
An arbitrary string to tracks the event that generated this request (e.g. 'signup').
An array of up to 9 tags you wish to associate with this request (and corresponding messages) for later analysis. Individual tags cannot be more than 30 characters in length.
Identify the campaign that refers traffic to a specific website, and attributes the browser's website session.
A unique ID used to correlate this request to processing on your servers. Note: Courier does not verify the uniqueness of this ID.
The ID of the subscription topic you want to apply to the message. If this is a templated message, it will override the subscription topic if already associated
An object whose keys are valid provider identifiers which map to an object.
Allows you to customize which channel(s) Courier will potentially deliver the message. If no routing key is specified, Courier will use the default routing configuration or routing defined by the template.
all, single A list of channels or providers to send the message through. Can also recursively define sub-routing methods, which can be useful for defining advanced push notification delivery strategies.
Time in ms to attempt the channel before failing over to the next available channel.
no-escalation, delivered, viewed, engaged Defines the time to wait before delivering the message. You can specify one of the following options. Duration with the number of milliseconds to delay. Until with an ISO 8601 timestamp that specifies when it should be delivered. Until with an OpenStreetMap opening_hours-like format that specifies the Delivery Window (e.g., 'Mo-Fr 08:00-18:00pm')
The duration of the delay in milliseconds.
An ISO 8601 timestamp that specifies when it should be delivered or an OpenStreetMap opening_hours-like format that specifies the Delivery Window (e.g., 'Mo-Fr 08:00-18:00pm')
"Expiry allows you to set an absolute or relative time in which a message expires. Note: This is only valid for the Courier Inbox channel as of 12-08-2022."
A duration in the form of milliseconds or an ISO8601 Duration format (i.e. P1DT4H).
An epoch timestamp or ISO8601 timestamp with timezone (YYYY-MM-DDThh:mm:ss.sTZD) that describes the time in which a message expires.
CREATED, PROCESSING, COMPLETED, ERROR