Skip to main content
Base URL: https://core-api.vanish.trade SOL Native Address: 11111111111111111111111111111111 Authentication: All endpoints require an x-api-key header. Every endpoint except the two commit endpoints also requires a signed message - see Signing. The Vanish Core injection process adds approximately 200ms to finality. Your instructions are injected into Vanish’s transaction wrapper, keeping you in full control over route, slippage, and execution.

​
How It Works

When a trade or a lending action is submitted, Vanish:
  1. Advances funds from its trading accounts to a one-time wallet.
  2. Wraps your transaction - your instructions are passed through unchanged, with settlement instructions added around them. Whichever DEX, aggregator, or lending provider you chose is untouched.
  3. Routes the transaction via Jito bundle or returns a signed payload for self-broadcast.
  4. Settles atomically at the end. If any instruction fails, everything reverts - failed transactions only cost the base network fee.
The two flows differ only in how long the one-time wallet lives:
The two commit endpoints are not interchangeable. Commit deposits, trades, and withdrawals at /commit; commit lending actions at /borrow/commit.

​
Compliance

Vanish operates on a same wallet in, same wallet out model: the user’s connected wallet is the only address you can deposit from and the only address withdrawals are returned to. This is enforced at the protocol level and cannot be bypassed - see Compliance. If a deposit commit returns rejected, it failed compliance or risk screening. Funds are refunded to the originating wallet after extended screening completes; do not re-attempt until the refund is confirmed.

​
Handling Interrupted Flows

A transaction that is submitted but never committed stays in a pending state. Each API has its own recovery pair, and both commit endpoints are idempotent: Call both on startup - see Recovering Pending Commits for code.

​
Amounts

All amounts are denominated in lamports - the smallest unit of SOL (1 SOL = 1,000,000,000 lamports). SPL token amounts use the token’s own decimal precision. On a trade, a lower loan_additional_sol may work if the target token’s ATA already exists in the user’s wallet - but the recommended value is safe for all cases.

​
Next Steps

Signing

One prefix, six formats. The exact Details: line for every endpoint.

Trading

Deposit, trade privately, and withdraw.

Lending

Open a position, use the funds, then settle.