Developers
Know the shape before you build.
This page explains the concepts and shows illustrative request shapes. The API reference and SDKs are not yet published, so no endpoints, versions or libraries are claimed.
Concepts
How a connection works
- 01
Project and keys
A project provisions a sandbox environment (active) and a production environment (locked until go-live checks pass).
- 02
Consent
The customer authorises at their own bank. The consent record keeps bank, purpose, permissions and expiry.
- 03
Data and payments
Accounts, transactions and payments are read or created under that consent.
- 04
Webhooks
Signed event notifications with retry. Failed deliveries are visible and can be redelivered.
Request shapes
Illustrative examples
Switch language and copy. The host is a placeholder, not a real endpoint.
"tk-c"># Illustrative request shape. Not a published endpoint.
curl -X POST "https:">//{your-api-host}/v1/payments" \
-H "Authorization: Bearer $IRONLEDGE_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "amount": "2000.00", "currency": "GBP", "reference": "INV-1042" }'Developer console
API keys and webhooks, as built in the prototype
