Skip to main content
GET
/
notifications
/
{notification_guid}
/
deliverables
List deliverables
curl --request GET \
  --url https://int-data.moneydesktop.com/notifications/{notification_guid}/deliverables \
  --header 'MD-SESSION-TOKEN: <api-key>'
{
  "deliverable_notifications": [
    {
      "guid": "DNF-7aa13bdb-2866-ba38-b326-d9fb32268f9b",
      "channel": 1,
      "channel_name": "EMAIL",
      "content": "<html>...</html>",
      "has_been_delivered": false,
      "delivered_at": null,
      "delivered_on": null
    }
  ]
}
List all deliverables for a notification.

Authorizations

​
MD-SESSION-TOKEN
string
header
required

MX Session Token

  • Request an API token using the read API token endpoint in the MX SSO API.
  • Exchange an API token for a session token.
    • A session token is obtained by sending a POST request to /sessions
    • The session token will be used in each request made for the user. It should be passed in an MD-SESSION-TOKEN HTTP header as shown below.
    • This session token is valid for 30 minutes from the time it was created. The 30 minute expiration counter is refreshed with each call.
    • If you send a request with an expired session token you'll receive an error code of 4011.
curl -i https://int-data.moneydesktop.com/accounts \
-H 'MD-SESSION-TOKEN: CWforZl1Vn2vC_v6H4rnQRT1DoWpDouJAV-_5TBmiQRAtA8rsOG_BoajTiOSsL0A3bd-bmHXlA-eQzc9ywItKg' \
-H 'Content-Type: application/vnd.mx.nexus.v1+json' \
-H 'Accept: application/vnd.mx.nexus.v1+json'

In documentation code examples, replace <API_KEY_VALUE> with the session token.

Path Parameters

​
notification_guid
string
required

The unique identifier for notifications. Defined by MX.

Response

200 - application/vnd.mx.nexus.v1+json

OK

​
deliverable_notifications
object[]