See how a transaction’s spend was allocated across providers and the internal shadow transactions created for lineage.
curl --request GET \
--url http://localhost:5001/transactions/{transaction_id}/lineage \
--header '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"
}
]
}
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: Secure your Blnk server
fund_allocation[].amount values are returned as strings in minor units.curl --request GET \
--url http://localhost:5001/transactions/{transaction_id}/lineage \
--header '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"
}
]
}
Was this page helpful?
curl --request GET \
--url http://localhost:5001/transactions/{transaction_id}/lineage \
--header '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"
}
]
}