TigerBeetle operations

Parix exposes TigerBeetle operations through one versioned HTTP route:

POST /api/v1/databases/{databaseId}/tb/{operation}

The route authenticates the caller, verifies database access, resolves the provider gateway target, and executes the operation through the TigerBeetle gateway service.

Use this page as reference for operation names and payload limits. Use the database Query page for browser-based experiments.

Supported operations

The implementation supports:

• create_accounts
• create_transfers
• lookup_accounts
• lookup_transfers
• get_account_balances
• get_account_transfers
• query_accounts
• query_transfers

Read operations require db:read. Create operations require db:write.

Payload limits

TigerBeetle IDs and amounts are represented as non-negative integer-like values. JSON callers should send them as strings when values can exceed JavaScript's safe integer range.

Batch-oriented operations accept up to 8190 items. Lookup and transfer query payloads must include at least one ID or a valid query object.

Example read-only request:

curl -X POST "https://dev.parix.io/api/v1/databases/<database-id>/tb/query_accounts" \
  -H "content-type: application/json" \
  -H "x-api-key: $PARIX_API_KEY" \
  -d '{"limit":100,"flags":0}'

Write result behavior

Write requests can return TigerBeetle batch result details. When TigerBeetle reports write conflicts, the API returns a conflict response with tbResults so callers can inspect per-item outcomes.

Query explorer

The database Query page uses the same operation set through a React Router action. It defaults to Query accounts and displays returned rows in a browser grid, making it a useful read-only smoke test before wiring an application.