The BlooBank Transactions Engine API is the canonical entry point for wallet management and payment-order orchestration on the BlooBank platform. This reference documents every endpoint, schema, and error contract.Documentation Index
Fetch the complete documentation index at: https://developers.bloobank.com/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
Authentication
Every request is authenticated via the BlooBank Access Protocol — four required headers (X-Access-Key, X-Access-Timestamp, X-Access-Request-Id, X-Access-Signature) carrying an ECDSA signature over the canonical request.
Read the Access Protocol guide
How to sign a request — generate keys, build the canonical string, attach the headers.
Conventions
These contracts are shared across every endpoint. Read them once and rely on them everywhere.HTTP
Methods, status codes, content types.
Errors
Canonical error envelope and reason codes.
Pagination
Cursor-based pagination via opaque page tokens.
Filtering
SFS-1 filter expressions for list endpoints.
Resources
Wallets
Tenant-scoped balance containers — the isolation boundary for payments and ledger.
Payment Orders
Inbound (
IN) and outbound (OUT) payments routed through provider networks.