APEX Custody Integration API

The APEX Custody Integration API provides programmatic access to the custody platform for managing accounts, wallets, chains, networks, documents, and more. All communication uses JSON over HTTPS with Bearer token authentication.

Base URL

https://integration.test-custody.tokenizationtr.com/v1

Quick Start

1. Obtain an API Key

API keys are generated from the APEX Custody dashboard. Each key is tied to a specific node and role with defined permissions.

2. Authenticate

Exchange your API key for a JWT access token:

curl -X POST https://integration.test-custody.tokenizationtr.com/v1/auth/authenticate \
  -H "Content-Type: application/json" \
  -H "X-Target-Server: authentication" \
  -d '{"api_key": "your-api-key-here"}'

Response:

{
  "token": "eyJhbGciOiJIUzI1NiIs...",
  "refresh_token": "eyJhbGciOiJIUzI1NiIs...",
  "expires_at": "2025-01-01T01:00:00Z",
  "created_at": "2025-01-01T00:00:00Z"
}

3. Make Authenticated Requests

Use the token as a Bearer token in subsequent requests:

curl https://integration.test-custody.tokenizationtr.com/v1/accounts \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIs..." \
  -H "X-Target-Server: accounts"

Common Headers

Header	Required	Description
Authorization	Yes (except auth endpoints)	Bearer token: Bearer <token>
Content-Type	Yes (for request bodies)	application/json (or multipart/form-data for file uploads)
X-Target-Server	Yes	Gateway routing header. Routes requests to the correct backend service. See the value for each endpoint in its documentation.

X-Target-Server Header

Every request must include the X-Target-Server header. This header tells the API gateway which backend service should handle the request. Each endpoint's documentation specifies the correct value (e.g., authentication, accounts, wallets, chains).

API Versioning

The API is currently at v1. All endpoints are prefixed with /v1.

Content Type

• Request bodies: application/json (unless uploading files, which use multipart/form-data)
• Responses: application/json (unless downloading files, which return application/octet-stream)

Resources

Resource	Description
Authentication	API key exchange, token refresh
Accounts	Account CRUD operations
Chains	Blockchain chain information
Networks	Network information per chain
Network Currencies	Token/currency information per network
Wallets	Wallet management, withdrawals
Wallet Rules	Auto-transfer and transfer limit rules
Auto-Transfer Transactions	Approve/reject auto-transfer transactions
Documents	Compliance document management
Nodes	Node user management

Cross-Cutting Concerns

• Pagination -- All list endpoints use a standard pagination pattern.
• Error Handling -- Standard HTTP error codes and response format.