Transactions
View transaction lineage
See how a transaction’s spend was allocated across providers and the internal shadow transactions created for lineage.
GET
/
transactions
/
{transaction_id}
/
lineage
curl -X GET "http://localhost:5001/transactions/{transaction_id}/lineage" \
-H "X-blnk-key: <api-key>"
{
"transaction_id": "txn_8d2ce2f0-0d75-4a91-9d43-2ad2c2e6b9ad",
"fund_allocation": [
{ "provider": "stripe", "amount": "2500" }
],
"shadow_transactions": [
{
"transaction_id": "txn_shadow_123",
"reference": "ref_002_release_stripe_0",
"precise_amount": "2500",
"currency": "USD",
"status": "APPLIED"
}
]
}
{
"error": "Transaction with ID 'txn_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' not found",
"error_detail": {
"code": "TXN_NOT_FOUND",
"message": "Transaction with ID 'txn_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' not found",
"details": {}
}
}
If you’re using the auto-provisioned
Enterprise Core instance included with your Production License deployment, set the base URL to: https://ENTERPRISE_PUBLIC_URL/core.If you’re connecting to a different Core instance, use the publicly accessible base URL for that instance instead.Authorization
If set, the API uses an API key for authentication. Include the following header in your requests:X-blnk-key: <api-key>.
Replace <api-key> with your secret API key. Ensure the key is kept secure and not exposed in public repositories or client-side code.
See also: Scoped API keys and Secure your Blnk server.
Path
string
required
Specifies the unique ID of the transaction whose lineage you want to retrieve.
Response
string
required
The ID of the transaction being queried.
array
Fund allocation breakdown for debit transactions from a lineage-enabled balance.
array
required
Internal shadow transactions created for lineage tracking (each item is a transaction object).
fund_allocation[].amount values are returned as strings in minor units.curl -X GET "http://localhost:5001/transactions/{transaction_id}/lineage" \
-H "X-blnk-key: <api-key>"
{
"transaction_id": "txn_8d2ce2f0-0d75-4a91-9d43-2ad2c2e6b9ad",
"fund_allocation": [
{ "provider": "stripe", "amount": "2500" }
],
"shadow_transactions": [
{
"transaction_id": "txn_shadow_123",
"reference": "ref_002_release_stripe_0",
"precise_amount": "2500",
"currency": "USD",
"status": "APPLIED"
}
]
}
{
"error": "Transaction with ID 'txn_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' not found",
"error_detail": {
"code": "TXN_NOT_FOUND",
"message": "Transaction with ID 'txn_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' not found",
"details": {}
}
}
Need help?
We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool. To ask questions or discuss issues, please contact us or join our Discord community.Was this page helpful?
⌘I
curl -X GET "http://localhost:5001/transactions/{transaction_id}/lineage" \
-H "X-blnk-key: <api-key>"
{
"transaction_id": "txn_8d2ce2f0-0d75-4a91-9d43-2ad2c2e6b9ad",
"fund_allocation": [
{ "provider": "stripe", "amount": "2500" }
],
"shadow_transactions": [
{
"transaction_id": "txn_shadow_123",
"reference": "ref_002_release_stripe_0",
"precise_amount": "2500",
"currency": "USD",
"status": "APPLIED"
}
]
}
{
"error": "Transaction with ID 'txn_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' not found",
"error_detail": {
"code": "TXN_NOT_FOUND",
"message": "Transaction with ID 'txn_f482a1b3-6c2d-4e89-a17b-3d5e8f2a1c94' not found",
"details": {}
}
}