Connect Sinch Engage (formerly MessageMedia) with an API key and secret, and receive delivery status by webhook.
Sinch Engage is MessageMedia rebranded after the Sinch acquisition. It is a different product from , which is its own integration with its own credentials.The catalog also lists Sinch Engage / MessageMedia under the provider key messagemedia. It takes the same API key and secret and sends the same way, so an integration already on messagemedia keeps working and needs no migration. Use sinch-engage for a new integration.
covers the two levels and which one wins.Overrides change the request body, config, and headers Courier sends to Sinch Engage. Override apiKey, apiSecret, isHmacEnabled, and url via config, and any SendMessages body field via body.
Courier gives the integration a unique webhook URL. Point the provider’s 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 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.
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.