Clients with Pending Notes

This endpoint returns the count of customers whose applications are neither approved nor declined — that is, they remain in a pending state. Results can be filtered by agent IDs, ISO ID, and profile IDs. The response provides separate counts for banking and merchant customer types.

Endpoint

POST /api/Widget/pending

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint to populate dashboard widgets or administrative reports that display how many customers are awaiting review or approval. It is particularly useful for partner portals where agents or ISO managers need a real-time snapshot of their pending customer pipeline, broken down by banking and merchant profile types.

Request Body

The request body accepts one of the following schemas. All share the base filter fields (agentsId, isoId, profileIds) and extend them with additional date or status fields depending on the use case.

Base Fields (shared across all request types)

Extended Fields — widgetrequest variant

Extended Fields — reportrequest variant

Extended Fields — widgetreportrequest variant

Extended Fields — balancesrequest variant

Extended Fields — rewardsreportrequest variant

Minimal request body example (base filters only):

{
  "agentsId": [101, 102],
  "isoId": 5,
  "profileIds": [201, 202, 203]
}

Widget date-range request example:

{
  "agentsId": [101],
  "isoId": 5,
  "profileIds": [201],
  "fromDate": "2026-01-01T00:00:00Z",
  "toDate": "2026-06-01T00:00:00Z"
}

Response

200 OK

{
  "bankingCount": 47,
  "merchantCount": 12
}

Error Codes

Common Mistakes

• Omitting fromDate and toDate when using the widgetrequest or balancesrequest schema — both fields are required for those variants.
• Passing an empty agentsId array expecting it to return no results; an empty or null array means no agent filter is applied and all agents are included.
• Assuming a null response for bankingCount or merchantCount indicates an error — null values simply mean no matching pending customers were found for that category.
• Sending reportDates as a single string instead of an array when using the widgetreportrequest variant.
• Using an applicationStatus value outside the defined enum list, which will result in a 400 validation error.

Related Endpoints

• POST /api/Widget/approved — Returns the count of customers with approved application status
• POST /api/Widget/declined — Returns the count of customers with declined application status
• POST /api/Widget/totalClients — Returns the total count of all customers regardless of status
• POST /api/Widget/newClients — Returns the count of newly created customer records within a date range

Example

curl -X POST https://api.banking.netevia.dev/api/Widget/pending \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "agentsId": [101, 102],
    "isoId": 5,
    "profileIds": [201, 202],
    "fromDate": "2026-01-01T00:00:00Z",
    "toDate": "2026-06-01T00:00:00Z"
  }'