Skip to main content
Pre-release — contact your Fortary account team for access.
Illustrative reference. These examples show the shape of the API and are provided for early evaluation while it is still being finalized. Field names and response details may change before the API is released. A complete reference, generated directly from the live API, will replace these examples once it is available.
The v1 API is read-only and served at https://customer-api.fortary.io. Every path begins with the version segment /v1, every response uses the stable identifiers and data formats described below, and every list is cursor-paginated.

​
Authentication

Send your API key as a bearer token in the Authorization header: 
curl https://customer-api.fortary.io/v1/vaults \
  -H "Authorization: Bearer fkc_..."
See the Authentication guide for how to create and manage keys, and Scopes for what a key is allowed to do (vault:read in v1).

​
Conventions

The same rules apply across every endpoint — learn them once and you can read any response:
  • Authorization & status codes — how access is decided, and what 401, 403, and 404 mean.
  • Identifiers & data formats — opaque vault IDs, friendly network names, structured asset IDs, string amounts, and Z-suffixed timestamps.
  • Pagination — how to page through lists with nextCursor.
  • Errors — the error envelope and how to handle failures.
  • Rate limiting — per-credential limits and the X-RateLimit-* headers.

​
Endpoints

MethodPathDescription
GET/v1/vaultsList the vaults the credential can access
GET/v1/vaults/{vaultId}Retrieve a single vault
GET/v1/vaults/{vaultId}/balancesList a vault’s asset balances
GET/v1/vaults/{vaultId}/transactionsList a vault’s transaction history
GET/v1/vaults/{vaultId}/addressesList a vault’s deposit addresses
GET/v1/networksList the networks available to your organization
GET/v1/assetsList the assets Fortary supports