Latest API Updates

What the Across API changes, and the four calls that move money across chains.

The Across API replaces a wide surface of endpoints with four calls that are the same for every transfer: discover, price, execute, track. Whatever is moving and wherever it is going, the shape of the integration does not change.

Staging. The latest Across API is available in a staging environment today.

The four calls

CallPurpose
1GET /v1/capabilitiesWhat can move between two chains right now, and why anything unavailable is unavailable
2POST /v1/quotesPrice one exact transfer. Returns an expiry and the payload to sign
3POST /v1/quotes/{orderId}/executionsSubmit the signed authorization
4GET /v1/transfers/{orderId}Follow the money to a settled outcome

All four are served from one host, under /v1:

https://api.staging.across.to

What changes

One identifier, end to end. The quoteId you priced, the transferId you executed, and the Across order id are the same value. There is no lookup to get from a quote to its transfer.

Capabilities replace route lists. Rather than fetching chains, tokens and routes separately and intersecting them yourself, GET /v1/capabilities answers the corridor question directly — and tells you why something is unavailable instead of omitting it.

Funding method is explicit. You request approval, permit2 or erc3009. deposit_address, account_abstraction and contract are chosen by the server and returned on the quote. Whatever the method, the quote hands you a nextActions list and you dispatch on kind once.

Status is two-dimensional. A transfer carries both isTerminal (Across is done with it) and finalized (the chain state can no longer reorg), plus a support-safe description you can show a user directly. Branch your logic on state and reason; never parse description.

Bodies are strict. Unknown request fields are rejected rather than silently ignored, so a typo surfaces immediately instead of changing behaviour quietly.

Next

On this page