Returns a count of clients who made no spending transactions within a specified date range.
Count Clients with No Spending by Date
This endpoint counts the number of clients who did not make any spending transactions within a specified date range. Results can be filtered optionally by ISO ID or agent ID to narrow the scope to a specific sales organization or agent. The response separates counts into banking and merchant client categories.
Endpoint
GET /api/Widget/NonSpendingbyDate
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint to identify customer inactivity within a given time window. It is particularly useful for partners building re-engagement campaigns, monitoring dormant accounts, or generating business intelligence reports on spending behavior across their client base.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| fromDate | string (date-time) | No | The start date of the non-spending period to query (ISO 8601 format). |
| toDate | string (date-time) | No | The end date of the non-spending period to query (ISO 8601 format). |
| isoId | integer (int32) | No | Filter results by ISO (Independent Sales Organization) ID. |
| agentId | integer (int32) | No | Filter results by agent ID. |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| bankingCount | integer (int32), nullable | Number of banking clients who had no spending transactions in the specified period. |
| merchantCount | integer (int32), nullable | Number of merchant clients who had no spending transactions in the specified period. |
{
"bankingCount": 142,
"merchantCount": 37
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Invalid date format supplied for fromDate or toDate |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions |
| 404 | Resource not found |
| 500 | Internal server error |
Common Mistakes
- Supplying dates in a non-ISO 8601 format (e.g., MM/DD/YYYY) instead of the expected date-time format (e.g.,
2024-01-01T00:00:00Z). - Omitting both
fromDateandtoDate, which may return unexpected or unscoped results — always specify a date range for meaningful data. - Confusing
isoIdwith an ISO country code; this field refers to the numeric ID of an Independent Sales Organization, not a country identifier.
Related Endpoints
GET /api/Widget/SpendingbyDate— Count clients who made spending transactions within a date rangeGET /api/Widget/ActiveClients— Retrieve a count of active clients
Example
curl -X GET "https://api.banking.netevia.dev/api/Widget/NonSpendingbyDate?fromDate=2024-01-01T00%3A00%3A00Z&toDate=2024-01-31T23%3A59%3A59Z&isoId=101&agentId=55" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"