Skip to main content

Prerequisites

Setup

In the MessageMedia console:
1

Create a new API key

Create a new API key.
2

Copy the API key and secret

Save the api_secret now. MessageMedia will not show it again.
In Courier, open the page, paste your credentials, and click “Save.”

MessageMedia API Key

Addressing a recipient and sending are the same on every SMS provider, so they are documented once: and .

Overrides

covers the two levels and which one wins. Overrides change the request body, config, and headers Courier sends to MessageMedia. Override apiKey, apiSecret, isHmacEnabled, and url via config, and any SendMessages body field via body.

Delivery tracking

Courier gives the integration a unique webhook URL. Point MessageMedia webhooks at it to sync delivery updates into Courier’s message logs. Copy the URL from the in Courier, then follow these steps in the MessageMedia console:
1

Create a new webhook

Select “New Webhook”.
2

Paste Courier's webhook URL

Paste the URL you copied.
3

Select the delivery report events

Under “Event”, select “Message is rejected”, “Message has failed”, and “Message is delivered” in Delivery reports.

MessageMedia Webhook Configuration

4

Map the webhook content

Under “Content”, map the fields passed to Courier’s webhook endpoint.
Only messageId, receivedTimestamp, status, and statusCode are supported.

Webhook Content Mapping

Delivery updates now appear in the message logs.

Delivery Confirmation

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.