Get a list of all low balance alerts for a customer
🚧 Coming soon
The GET {URI}/customers/{customerIdentifier}/accounts/{accountIdentifier}/lowbalance
endpoint allows you to retrieve all low balance alerts that have been configured for a specific account under a customer. These alerts help ensure that stakeholders are notified when account balances fall below defined thresholds, enabling proactive funding and uninterrupted reward distribution. This endpoint is especially useful for auditing existing alerts, reviewing notification settings, or confirming that alerts are properly configured for critical accounts.
Use case
Acme Wellness manages multiple reward accounts for its client, Zanzibar Health Group. One of these accounts has a low balance alert set to notify the HR team when funds drop below $100. To ensure the alert is still active and correctly configured, Acme uses this endpoint to retrieve all low balance alerts associated with the account. By reviewing the alert settings, Acme can confirm the alert threshold is accurate, the correct recipients are being notified, and no duplicate or outdated alerts exist.
Use the following endpoint to get a list of all low balance alerts for a specific account:
Endpoint | Purpose |
---|---|
GET {URI}/customers/{customerIdentifier}/accounts/{accountIdentifier}/lowbalance | Get a list of all low balance alerts for a specific account |
The following values are part of your URL path for this API request. customerIdentifier
is a string used to identify the Group (Customer) that contains the account you are transacting from:
Path param | Data type | Requirement | Description |
---|---|---|---|
customerIdentifier | string | required | A unique identifier for the customer under which you are seeking details. The string must have 5-100 characters. (????) |
accountIdentifier | string | required | Specify the exact account to be monitored. The string must have 5-100 characters. (???) |
The following query parameters can be appended to the end of URL to pass additional information to the server
Query params | Data type | Requirement | Description |
---|---|---|---|
elementsPerBlock | int32 | optional | Specify the number of elements in a block to control how many items (or elements) are grouped together in a single block of data. It is an integer (int32) value. |
page | int32 | optional | Specify the page number to return; used for pagination—a way to split large sets of data into smaller, more manageable chunks or pages. |
balanceAlertDisplayName | string | optional | A friendly name for this low balance alert which helps identify and describe the purpose of the alert when viewed in the Tango portal or through API responses. |
balanceAlertThreshold | string | optional | The specific balance amount at which a low balance alert will be triggered for an account. When the account’s balance falls below this threshold, the system will activate the alert and notify the designated recipients.. |
balanceAlertNotification | array of objects | optional | Used to define who should be notified when a low balance alert is triggered for an account. It's an array of objects, where each object typically contains an email address that will receive the alert. |
Here is an example of the returned payload:
{
"page": {
"size": 0,
"totalElements": 0,
"totalPages": 0,
"number": 0
},
"lowBalanceAlerts": [
{
"createdAt": "2025-07-15T17:00:04.933Z",
"balanceAlertID": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"customerIdentifier": "string",
"accountIdentifier": "string",
"balanceAlertDisplayName": "string",
"balanceAlertThreshold": 0,
"balanceAlertNotification": [
{
"emailAddress": "string"
}
]
}
]
}
The possible response codes for this endpoint are as follows. For details, see i18nkey codes and their error messages:
Response code | Meaning |
---|---|
200 | The request was successful. |
400 | The server could not understand the request due to invalid syntax. |
401 | Authentication is required and has either not been provided or failed. |
403 | The server understood the request but refuses to authorize it. |
422 | The server understands the request but cannot process it due to semantic errors. |
500 | Something went wrong on the server, but the server cannot be more specific about what the exact problem is. |
503 | The server is currently unable to handle the request due to temporary overload or maintenance. |
Updated about 15 hours ago