Skip to main content
POST
/
v1
/
notification
{
  "accountId": "1234567890",
  "branchCode": "752001",
  "customerNumber": "ABCDEFGH123456789",
  "id": "1234567890",
  "status": "ACCOUNT_BLOCKED",
  "subType": "STATUS_CHANGE",
  "type": "ACCOUNT"
}

{
  "description": "<string>",
  "id": "<string>"
}
{
  "accountId": "1234567890",
  "branchCode": "752001",
  "customerNumber": "ABCDEFGH123456789",
  "id": "1234567890",
  "status": "ACCOUNT_BLOCKED",
  "subType": "STATUS_CHANGE",
  "type": "ACCOUNT"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Notification information. The fields are different depending which type of notification it is.

​
id
string
required

Unique ID for a notification assigned by Enfuce

Example:

"1234567890"

​
type
enum<string>
required

Corresponds to the entity represented in other parts of Enfuce API. Note: The INVOICE enum is available only for fleet cards.

Available options:
ACCOUNT,
CARD,
TRANSACTION,
AUTHORIZATION_HOLD,
TOKENIZATION,
EMVSCRIPT,
INVOICE,
FRAUD_CASE
​
branchCode
string

Your Institution Identifier assigned by Enfuce. For example, this can be used to determine the Sender ID for SMS messages.

Example:

"752001"

Response

A new notification event created

​
description
string

Short description of the result of the action

​
id
string

Will contain the ID of the resource that has been created or updated