> ## 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.

# API Reference

> BlooBank Transactions Engine API — try it live, copy code, inspect schemas.

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.

## Base URL

```
https://txengine.bloobank.com/txengine/v1
```

## 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.

<Card title="Read the Access Protocol guide" icon="shield-check" href="/get-started/authentication/overview" horizontal>
  How to sign a request — generate keys, build the canonical string, attach the headers.
</Card>

## Conventions

These contracts are shared across **every** endpoint. Read them once and rely on them everywhere.

<CardGroup cols={2}>
  <Card title="HTTP" icon="globe" href="/api-reference/conventions/http">
    Methods, status codes, content types.
  </Card>

  <Card title="Errors" icon="bug" href="/api-reference/conventions/errors">
    Canonical error envelope and reason codes.
  </Card>

  <Card title="Pagination" icon="arrow-down" href="/api-reference/conventions/pagination">
    Cursor-based pagination via opaque page tokens.
  </Card>

  <Card title="Filtering" icon="filter" href="/api-reference/conventions/filtering">
    SFS-1 filter expressions for list endpoints.
  </Card>
</CardGroup>

## Resources

<CardGroup cols={2}>
  <Card title="Wallets" icon="wallet" href="/api-reference/wallets/overview">
    Tenant-scoped balance containers — the isolation boundary for payments and ledger.
  </Card>

  <Card title="Payment Orders" icon="money-bill-transfer" href="/api-reference/payment-orders/overview">
    Inbound (`IN`) and outbound (`OUT`) payments routed through provider networks.
  </Card>
</CardGroup>