Automate vaults with plain HTTP.

Overview

The Infinite Trading API lets software do what a vault manager does by hand: trade, approve, lend, provide liquidity and run strategies. You send a short HTTP request, and the API builds, routes, signs and submits the on-chain transactions.

It sits in front of Chamber vaults (formerly dHEDGE). A Chamber vault is a smart contract that holds investor funds. A designated tradercan trade the vault's whitelisted assets but cannot withdraw investor funds. The API gives your code that trader role, so a strategy can run around the clock while custody stays in the vault.

How it works

Every request follows the same path from your code to the chain.

1. Your clientA script, bot or app sends an HTTPS request with your API key.
2. GatewayTLS, rate limiting and an allowlist of public endpoints.
3. ValidationChecks the network, protocol, vault address and key, and resolves your gas wallet.
4. ExecutorPicks a venue through a per-network fallback chain, builds and submits the transaction.
5. On-chainThe gas wallet acts as the vault's trader and the result is returned as JSON.

Reads, such as poolComposition or getCandles, stop before the executor and never send a transaction. Anything that moves funds is signed by the gas wallet linked to your key, never by a shared signer.

Core concepts

Five ideas explain almost every endpoint.

Quickstart

From nothing to a first trade. Start on a small vault.

1. Get a gas wallet and API key

   A gas wallet is a dedicated hot wallet that pays gas and acts as the vault's trader. You have two options.

   Option A: create a new one

   One call generates a fresh wallet and its API key. The private key is returned once, so store it securely right away. This endpoint is not listed in Swagger.

   curl https://api.infinitetrading.io/createGasWallet
   
   # {
   #   "status": ["success"],
   #   "address": ["0x…"],
   #   "private_key": ["…64 hex characters, no 0x prefix"],
   #   "apiKey": ["…uuid"]
   # }

   Copy

   Option B: import an existing hot wallet

   Send its private key once to receive an API key. Do it over HTTPS from a trusted server, never from a browser, and only for a wallet that holds gas and nothing else.

   curl -X POST https://api.infinitetrading.io/getNewApiKey   -H "Content-Type: application/json"   -d '{"privateKey": "0x…"}'

   Copy
   One key per walletCalling getNewApiKey again issues a new key and revokes the old one immediately. Anything still using the old key stops working.

2. Fund it and make it the trader

   Send a small amount of native gas token (ETH, POL and so on) to the wallet on every network you will trade on. Then set it as the trader of your Chamber vault. The Managers console does both for you, including creating or importing the wallet. Check the balance any time with getGasBalance.

   curl "https://api.infinitetrading.io/getGasBalance?apiKey=KEY&network=base"

   Copy

3. Confirm the wiring

   curl "https://api.infinitetrading.io/isPoolTrader?apiKey=KEY&network=base&pool=0xVAULT&trader=0xGASWALLET"

   Copy

4. Read before you write

   Look at what the vault holds. This sends no transaction.

   curl "https://api.infinitetrading.io/poolComposition?apiKey=KEY&network=base&pool=0xVAULT"

   Copy

5. Approve, then trade

   Approve the asset once, then swap a share of the balance.

   curl -X POST "https://api.infinitetrading.io/approve?apiKey=KEY&network=base&pool=0xVAULT&asset=USDC"
   
   curl "https://api.infinitetrading.io/vaultTrade?apiKey=KEY&network=base&pool=0xVAULT&from=USDC&to=WETH&share=25"

   Copy

Conventions

Most endpoints accept both GET and POST. Parameters can go in the query string or the JSON body, and are merged.

Errors & limits

Check the body, not just the HTTP status.

{
  "status": ["fail"],
  "status_code": ["1000"],
  "message": ["Unrecognized network"]
}

Execution errors and rate limits

Failures while executing (as opposed to validating) return HTTP 400 with a flat object that carries status, status_code and error_type.

The gateway allows roughly 30 requests per minute with a burst of 20; beyond that you receive an HTML 503, which is throttling and not an outage. The API itself also limits requests per minute. Back off and retry.

Endpoints

44 endpoints in 9 groups. Each group lists what it is for and what you can build with it. Parameters marked * are required. Use the interactive Swagger for request builders and live responses.

Recipes

Common ways to combine endpoints.

Best practices

Habits that keep automated trading safe.

• Use a dedicated gas wallet. Fund it with gas only. The vault holds the money.
• Keep keys server-side. Never ship an API key in browser code or a public repo.
• Start small and read first. Use poolComposition, previewIndexBot and dryRun before anything that moves funds.
• Prefer share over amount so a strategy scales with the vault instead of hard-coding sizes.
• Watch gas. Poll getGasBalance and alert before the wallet runs dry.
• Handle failures. Check the body for status, retry 503s with backoff and make writes idempotent on your side.
• Rotate on suspicion. Request a new key; the old one is revoked at once.