Overview

Delta V2 cuts client-side work out of Delta integrations: the server builds EIP-712 orders ready to sign, prices come back as a route with alternatives, order history is paginated, and one status field follows an order end to end.

Build new Delta integrations on V2. The server carries most of the protocol work, so your client stays thin:

• Orders come back from POST /v2/delta/orders/build as EIP-712 typed data ready to sign. You never compose domain, types, and value yourself.
• GET /v2/delta/prices recommends a route and lists alternatives, so users can pick a different bridge or path.
• Order history is paginated: GET /v2/delta/orders returns { data, total, page, limit, hasMore }.
• A single status field covers the whole lifecycle (PENDING, AWAITING_SIGNATURE, ACTIVE, SUSPENDED, CANCELLING, BRIDGING, COMPLETED, FAILED, EXPIRED, CANCELLED, REFUNDED), replacing the V1 split between status and bridgeStatus.
• Partner fees are resolved server-side. Pass partner / partnerAddress / partnerFeeBps raw; the server validates and encodes them, and the getPartnerFee round-trip disappears.

Lifecycle

1. Price

   GET /v2/delta/prices — returns route, alternatives, and the spender contract address.

2. Approve

   ERC-20 approve(spender, amount) against price.spender, or sign Permit / Permit2 with the same verifyingContract. Native tokens skip this.

3. Build

   POST /v2/delta/orders/build — returns { toSign: { domain, types, value }, orderHash }.

4. Sign

   Sign toSign with signTypedData on the user’s wallet.

5. Submit

   POST /v2/delta/orders — passes order: toSign.value and signature to the relayer.

6. Poll

   GET /v2/delta/orders/{orderId} until status === "COMPLETED" (or a terminal failure).

Endpoints

Method	Path	Purpose
GET	/v2/delta/prices	Recommended route + alternatives, same-chain or crosschain
GET	/v2/delta/prices/bridge-routes	Supported (srcChainId, destChainId, tokens) triples
GET	/v2/delta/prices/bridge-protocols	Active bridge protocols (slug, name, icon)
GET	/v2/delta/prices/strategies/{chainId}	Delta yield strategies with APR
GET	/v2/delta/prices/is-token-supported	Quick token-support check
POST	/v2/delta/orders/build	Server-built EIP-712 typed data ready to sign
POST	/v2/delta/orders	Submit a signed order
POST	/v2/delta/orders/cancel	Sign-and-post cancellation
GET	/v2/delta/orders	List a user’s orders (paginated)
GET	/v2/delta/orders/{orderId}	Order by UUID
GET	/v2/delta/orders/hash/{hash}	Order by EIP-712 hash
GET	/v2/delta/orders/fillablebalance/...	Fillable balance for limit-order sizing
GET	/v2/delta/agents/list/{chainId}	List active auction agents

SDK shortcut

Every endpoint is wrapped by sdk.delta.*, which handles signing, partner-fee defaults, and the build → sign → post orchestration. For a 5-minute walkthrough see SDK → Delta.

Related pages

• Why Delta — protocol overview.
• SDK → Delta — TypeScript examples.
• Migrating from Delta V1 — endpoint-by-endpoint guide from the V1 surface.