Skip to main content
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, REFUNDING, CANCELLED, REFUNDED), replacing the V1 split between status and bridgeStatus.
  • Crosschain bridge refunds include a top-level refunds[] array once Velora verifies the refund transaction receipt. Each item carries tx, chainId, token, and raw-unit amount.
  • 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 status such as FAILED, EXPIRED, CANCELLED, or REFUNDED.

​
Endpoints

​
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.
Last modified on June 25, 2026