Update or add metadata to a resource. Metadata is merged with existing values; existing keys are overwritten, and new keys are added.
For in-depth information about Blnk’s ledger, balance, transaction, and identity APIs, see the Blnk Core docs.
Request structure
curl -X POST "https://api.cloud.blnkfinance.com/proxy/txn_c4e70eb8-e4d6-4e04-a2e2-92a43b969e0c/metadata?instance_id=YOUR_INSTANCE_ID" \
-H "Authorization: Bearer blnk_at_YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"meta_data": {
"myApp": {
"channel": "web",
"customer_id": "cust_abc123",
"approval_status": "approved"
}
}
}'
The resource ID to update. Can be a ledger_id, balance_id, transaction_id, or identity_id.
Bearer token for authentication. Format: Bearer <access_token>. Your OAuth key must include proxy:write scope (or *).
Metadata object to merge with existing metadata. Use a top-level key (e.g., your app name) to avoid conflicts with user-defined or other apps’ metadata.
Query parameters
The Blnk Core instance ID to target. Find this in Blnk Cloud under Instances.
Response structure
{
"meta_data": {
"myApp": {
"channel": "web",
"customer_id": "cust_abc123",
"approval_status": "approved"
}
}
}
The updated metadata object for the resource.
Need help?
If you’re having trouble with Blnk Cloud, don’t hesitate to send us a message via email at [email protected] or send us a message here.