Request & Response Format

The Haiku Enterprise API follows a strict JSON-based format for all requests and responses.

All requests must include the following header:

Content-Type: application/json

• All API requests must be sent in JSON format

• Any request that does not include the above header will be rejected

• All responses are returned in JSON format

• Responses include standard HTTP status codes to indicate success or failure

• The API provides detailed error messages to assist with debugging.

Example successful response:

{
  "status": "success"
  "data": {
    "example_key": "example_value"
  }
}

Example error response:

{
  "status": "error"
  "message": "Invalid request parameters",
  "code": 400
}

Token iid Format

Haiku uses a standardised token identifier (iid) format to specify assets:

chainName:tokenAddress

Example:

arb:0xaf88d065e77c8cC2239327C5EDb3A432268e5831 --> USDC on Arbitrum (chain 42161)

Native Token Format

Haiku uses a special elastic address to represent native tokens (e.g. ETH) - e.g. arb:0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee --> ETH on Arbitrum (chain 42161)

Elastic addresses are used to ensure consistency across chains without requiring unique token contracts for each network.

Haiku Enterprise API currently supports the following blockchains:

Additional chains are coming soon and developers should check Whats New for updates.

Haiku supports Uniswap's Permit2 architecture, allowing gas-efficient token approvals. Permit2 reduces transaction overhead, is more secure than traditional ERC-20 allowances, and simplifies user experience by eliminating unnecessary steps.

How it works

1. Users sign a Permit2 message approving token allowances

2. Haiku bundles the approval and trade transaction into one atomic execution

3. The transaction executes securely without multiple approve calls.

For more details, see: What Is Permit2? | Revoke.cash