Skip to main content
The Transit API returns ready-to-sign transaction calldata for cross-chain stablecoin transfers. The server handles quote generation, fee calculation, and ABI encoding — you get back a transaction object to sign and broadcast. All Transit endpoints are public and do not require authentication.

When to Use Transit

  • Cross-chain stablecoin movement — Transfer USDC, USDT, PYUSD, or USDG between supported chains
  • Backend transaction builders — Fetch calldata via API, sign and submit from any language
  • Custodial wallets — Get transaction data server-side, route to your signing infrastructure

Prerequisites

  • An EVM wallet with sufficient balance for the offer amount plus native gas
  • An HTTP client (curl, fetch, requests, etc.)

Endpoints

Integration Flow

1

Discover Routes

Query available asset pairs to find a route matching your source and destination chains.
2

Check Authorization

Call /v3/core/authorization to detect whether the offer token requires a permit signature, an approval transaction, or is already approved for the TransitStation contract.
3

Get Order Quote

Fetch signed calldata for the submitOrder transaction, including the messaging fee. If using permits, pass the signature and deadline.
4

Submit Transaction

Broadcast the transaction on the source chain with the returned to, data, and value.
5

Track Order

Poll the order status endpoint until fulfillment completes on the destination chain.

Supported Chains

Getting Started

Route Discovery

Find available asset pairs and check minimum order sizes.

Order Submission

Get quote calldata and submit cross-chain orders.

Order Tracking

Monitor order status and view execution history.

AI Coding Reference

Condensed reference for AI coding assistants.