Get rendered notification content using the Messages API

The Courier Messages API allows you to fetch the array of events of a message you've previously sent, including the rendered content by using the endpoint.

To fetch the content for a given message there are two API calls that you need to make

Fetch message history using GET /messages/{message_id}/history and the message ID that was returned in response to your send command.
Fetch message content using a root-relative URL

1. Fetch message history:

Message history can be fetched by calling the history endpoint or by calling the getMessageHistory function in our SDKs.

Message history will contain a RENDERED event that contains links to the rendered output for the message.

Here is an example rendered event:

2. Fetch message content:

The output section in the history response contains the root-relative URL that can be used to fetch the content that was rendered and sent to the provider. The output url must be appended to the Courier API host (https://api.courier.com).

Here is an example of a rendered push event:

Rendered content for Emails

html content is returned with a content-type of text/html and the response is raw HTML:

Here is an example header response set (note the content type at the top).

content-type: text/html
content-length: 32015
date: Tue, 26 Oct 2021 17:10:10 GMT
x-amzn-requestid: e9d54717-3cb0-4f1e-a47a-b64317738596
access-control-allow-origin: *
strict-transport-security: max-age=31536000;includeSubDomains;preload
x-amz-apigw-id: H01x2GapIAMFgnA=
x-content-type-options: nosniff
x-amzn-trace-id: Root=1-61783672-23906a806f14d99d7d10ee9e
access-control-allow-credentials: true
x-cache: Miss from cloudfront
via: 1.1 55429f2d64d86ac51a104a1c84030e14.cloudfront.net (CloudFront)
x-amz-cf-pop: SFO5-C1
x-amz-cf-id: TOmwTJ_vtG_PZ5EIxf0nSqJ9wz7YBcg0j0uRsMFqghDd0eY5-jB7jw==

And here is a sample response: