Skip to main content
GET
/
notifications
/
{notification_guid}
Read notification
curl --request GET \
  --url https://int-data.moneydesktop.com/notifications/{notification_guid} \
  --header 'MD-SESSION-TOKEN: <api-key>'
{
  "notification": {
    "created_on": "2022-04-01T12:58:08.000Z",
    "deep_link_guid": "BGT-e386a323-e452-47f2-b2fd-1ac3c18533de",
    "entity_guid": "BGT-e386a323-e452-47f2-b2fd-1ac3c18533de",
    "guid": "TF-b53294f5-2356-4782-9f81-ae064c42b40a",
    "has_been_viewed": false,
    "notification_type": 2,
    "notification_type_name": "BUDGET_OFF_TARGET",
    "subject": "You're projected to spend $1,920.07 more than you've budgeted for Fees & Charges. You've already spent $65.67 of $316.00.",
    "threshold": null
  }
}
Read a specific 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

notification
object