Overview
API Reference
Webhooks
Add Metadata
Attach multiple metadata key/value pairs to a business in a single request.
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/business/meta-data/add \
--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",
"meta_data": [
{
"name": "external_ref",
"value": "ref-001"
},
{
"name": "external_ref_secondary",
"value": "ref-002"
}
]
}
'{
"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 business. Required when the endpoint operates on a specific business.
"buss-2ef94c60-5a11-4d72-a3c1-5be7fab0123e"
Program API key. Accepted either in the api_key HTTP header or as this body field.
List of {name, value} pairs to persist alongside the entity.
Show child attributes
Show child attributes
curl --request POST \
--url https://api.sdev.banking.ingopayments.tech/api/v4/business/meta-data/add \
--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",
"meta_data": [
{
"name": "external_ref",
"value": "ref-001"
},
{
"name": "external_ref_secondary",
"value": "ref-002"
}
]
}
'{
"status": "success",
"message": "operation completed",
"data": {}
}