9. Integration Method Frame (Current Stack)

Baltex Protocol keeps partner integrations stable. The protocol expands the underlying route graph; the external methods and schemas remain consistent.

---

9.1 Authentication

Partner endpoints require an API key supplied via the x-api-key header.

---

9.2 Cross-Chain API (Summary)

Method	Path	Purpose	Notes
GET	/v1/cross-chain/available-currencies	Discover supported currencies/networks.	Includes address regex, explorers, confirmations, fixed-rate support.
GET	/v1/cross-chain/rate	Quote a standard or fixed-rate exchange.	flow=standard|fixed-rate; amount optional.
GET	/v1/cross-chain/rate/private	Quote a private exchange.	Requires privateType.
POST	/v1/cross-chain/exchange	Create standard exchange.	flow required; rateId required for fixed-rate (valid 1 minute).
POST	/v1/cross-chain/exchange/private	Create private exchange.	privateType: privatePlus (XMR only) or efficient (fast/cheap relay).
GET	/v1/cross-chain/exchange/status	Get exchange status by id.	Wrapper for standard/private status.
GET	/v1/cross-chain/exchange/list	List exchanges (last 24h) with filters.	Filter by status, networks, exchangeType.

9.3 DeFi API (Summary)

Currently documented DeFi networks: eth, sol, sui, sei, arbitrum, base, bsc, cchain, celo, linea, matic, op, sonic, uni.

---

Method	Path	Purpose	Notes
GET	/v1/defi/currency/info	Resolve token metadata by network + address.	Returns token info if exists.
GET	/v1/defi/available-currencies	List tokens for a network.	Supports page/limit pagination; network required.
GET	/v1/defi/quote	Quote an on-chain swap route.	Requires network, fromTokenAddress, toTokenAddress, amount, slippage, referrerFee.
POST	/v1/defi/transaction/swap	Build a transaction hash to sign.	Returns tx hash from provided data.
POST	/v1/defi/send/approve	Broadcast approval tx (if needed).	Partner provides signed tx payload.
POST	/v1/defi/send/swap	Broadcast swap tx.	Partner provides signed tx payload.
GET	/v1/defi/exchange/list	List DEX exchanges (last 24h) with filters.	Filter by status, fromToken, toToken, network.

9.4 End-to-End Sequence (Concept)

Across flows, the partner frame remains: quote → create → user deposit/sign → status until terminal.

---

Sequence Diagram

Figure 7. Unified partner interaction sequence (Cross-Chain + DeFi).

---

Interaction Steps

#	Actor	Call	Description
1	Partner/UI → Baltex API	GET /rate or /defi/quote	Request a quote for the desired swap.
2	Baltex API → Router	—	Internally computes the best route.
3	Baltex API → Partner/UI	quote response	Returns quote with rate, fees, and TTL.
4	Partner/UI → Baltex API	POST /exchange or /defi/transaction/swap	Creates the exchange and locks the plan.
5	Baltex API → Executor	create swap + lock plan	Hands off to the executor for leg dispatch.
6	Executor → Venues	execute legs	Dispatches fills and transactions to liquidity venues.
7	Partner/UI → Baltex API	GET /exchange/status or /defi/exchange/list	Polls status until a terminal state is reached.

---

Notes

• The partner frame is identical for Cross-Chain and DeFi flows — only the endpoint paths differ.

• The Router is internal to Baltex API; partners never call it directly.

• Step 7 (status polling) should continue until a terminal state (finished, failed, or refunded) is returned.