The Account Notification Service sends you instant notifications when changes occur in your payment account. You can also set up triggers for specific credit or debit entries. This helps enhance your business by providing instant insights into your account and enabling better decisions through personalized notifications.
In addition, with this API you receive notifications directly in your ERP or TMS software - no waiting or polling required.
## **Before you begin** Make sure you have a working sandbox account in the [Rabobank developer portal](https://developer.rabobank.nl/). Read [Get Started](https://developer.rabobank.nl/get-started) to set up an account and register an **Application**. **NOTE:** To use these API(s), a valid [TLS](https://developer.rabobank.nl/how-use-mutual-tls) certificate is required.
## **Using the API** After your account set up is complete, subscribe the Account Notification Service and the Authorization Services to your application.
Make sure to use the **Authorization** and **Token URL** as provided by the [**Authorization Services**](https://developer.rabobank.nl/using-premium-access-authorization-access-rabobank-apis).
**Tip**: To learn how to sign a request, read [**Signing requests for Rabobank APIs**](https://developer.rabobank.nl/signing-requests-rabobank-apis).
## **Request for subscriptions** Integrate with the subscription management endpoints so that you can retrieve, create, or update subscriptions. - To create a subscription, go to POST /subscriptions - To update a subscription, go to PUT /subscriptions/{subscriptionId} - To delete a subscription, go to DELETE /subscriptions/{subscriptionId} ## **Set up triggers** To set up triggers for specific events using the Account Notification Service (ANS) API, subscribe to events for receiving instant notifications. You can customize these triggers based on a set of rules such as range of amount, credit/debit, or a transaction attribute.
**Example request message:** ``` { "account": { "iban": "NL52RABO0125618484", "currencyCode": "EUR" }, "transactionCriteria": { "amount": { "minTransactionAmount": 100, "maxTransactionAmount": 500 }, "remittanceInformationUnstructured": "Invoice*" }, "endDate": "2024-12-01T14:07:56.302663", "pushUri": "https://tpp.com/notify" } ``` In the above example an amount range and transaction description is used with a wildcard.

A wildcard (*) is a character that can be used as a substitute for any of a defined subset of characters. In the context of the API ANS, a wildcard can be used to represent one or more characters when setting up triggers for specific entries. For example, you can use a wildcard to represent any transaction subscription name that starts with a specific letter or sequence of letters, this allows you to create more flexible and powerful triggers for receiving instant notifications.

## **Receive instant notification** When a subscribed event is triggered, you should instantly receive a notification using the location as specified in pushUri field. ``` { "subscriptionId": "59bca412-6d40-469f-9b39-59f4617e95dd", "timestamp": "2024-02-27T11:10:00", "notificationType": "TRANSACTION", "notificationId": "faDSUaiUTdjlI2rGEsjM3R9tb9V584bD5YLZyz6cB2uWVT__2DyDVGl4jqM2Zao60nesScBihGjMzHOSsJmQvw-uI4MHhalaUbU0.9" } ``` ## **Get transaction details** You can use the notificationId as received in the notification message to retrieve the transaction details.
After receiving the request, a response containing the transaction details is sent.

For each transaction that matches the notification subscription, a notification with corresponding notificationId is sent to the pushUri.