Program Transaction Summary
Return aggregate totals of program transactions bucketed over the given date range.
Authentication: send the program API key either in the api_key HTTP header or as an api_key JSON body field.
curl --request POST \
--url https://api.sdev.banking.ingopayments.tech/api/v4/balance/program-transaction-summary \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'api_key: <api-key>' \
--data '
{
"api_key": "YOUR_API_KEY",
"user_id": "user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef"
}
'{
"status": "success",
"message": "operation completed",
"data": {}
}Documentation Index
Fetch the complete documentation index at: https://developers.ingopayments.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Program API key identifying your integration. Pass as the api_key HTTP header (preferred) or as an api_key field in the JSON request body. Required on every request in addition to the HMAC Authorization header.
Body
Identifier of the target user. Required when the endpoint operates on a specific user.
"user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef"
Program API key. Accepted either in the api_key HTTP header or as this body field.
Inclusive lower bound of a date/time range (ISO 8601).
Inclusive upper bound of a date/time range (ISO 8601).
curl --request POST \
--url https://api.sdev.banking.ingopayments.tech/api/v4/balance/program-transaction-summary \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'api_key: <api-key>' \
--data '
{
"api_key": "YOUR_API_KEY",
"user_id": "user-8f3a2b1c-0e44-4f2d-9a11-7b23cc90d1ef"
}
'{
"status": "success",
"message": "operation completed",
"data": {}
}