Download Transaction Report
Generate a program-level transaction report for the given date range and optional direction filter.
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/transactions/report \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'api_key: <api-key>' \
--data '
{
"api_key": "YOUR_API_KEY",
"start_date": "2024-01-01T00:00:00Z",
"end_date": "2024-01-31T23:59:59Z"
}
'{
"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
Inclusive lower bound of a date/time range (ISO 8601).
Inclusive upper bound of a date/time range (ISO 8601).
Program API key. Accepted either in the api_key HTTP header or as this body field.
Filter by transaction direction.
credit, debit curl --request POST \
--url https://api.sdev.banking.ingopayments.tech/api/v4/transactions/report \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'api_key: <api-key>' \
--data '
{
"api_key": "YOUR_API_KEY",
"start_date": "2024-01-01T00:00:00Z",
"end_date": "2024-01-31T23:59:59Z"
}
'{
"status": "success",
"message": "operation completed",
"data": {}
}