Skip to main content
POST
/
transactions
/
business-contacts
List transactions involving a business's contacts
curl --request POST \
  --url https://api.sdev.banking.ingopayments.tech/api/v4/transactions/business-contacts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'api_key: <api-key>' \
  --data '
{
  "api_key": "YOUR_API_KEY",
  "business_id": "buss-2ef94c60-5a11-4d72-a3c1-5be7fab0123e"
}
'
{
  "status": "success",
  "message": "operation completed",
  "data": {
    "items": [
      {
        "id": "ltra-4f2d9a11-7b23-cc90-d1ef-8f3a2b1c0e44",
        "amount": "100.00",
        "currency": "usd",
        "category": "<string>",
        "method": "<string>",
        "originator_type": "<string>",
        "originator_id": "<string>",
        "description": "<string>",
        "posting_date": "2026-04-16T12:34:56.000Z",
        "reversed_transaction_id": "ltra-4f2d9a11-7b23-cc90-d1ef-8f3a2b1c0e44"
      }
    ],
    "pagination": {
      "page": 1,
      "per_page": 25,
      "total": 100,
      "sort": "created_at:desc",
      "search": "jane"
    }
  }
}

Authorizations

​
api_key
string
header
required

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

application/json
​
business_id
string
required

Identifier of the target business. Required when the endpoint operates on a specific business.

Example:

"buss-2ef94c60-5a11-4d72-a3c1-5be7fab0123e"

​
api_key
string

Program API key. Accepted either in the api_key HTTP header or as this body field.

​
payment_direction
enum<string>

Filter by transaction direction.

Available options:
credit,
debit
​
page
integer
default:1

Page number, 1-indexed. Defaults to 1 when omitted.

Required range: x >= 1
​
per_page
integer
default:10

Page size. Defaults to 10 when omitted.

Required range: 1 <= x <= 500

Response

Success.

​
status
enum<string>
required
Available options:
success
​
message
string
required
Example:

"operation completed"

​
data
object

Endpoint-specific payload; shape varies per operation.