Build
App Integration
Connect a frontend or backend app to signed swap flows without leaking server-only trust.
Application integration has one main rule: the app may collect intent and render state, but it should not own quote signer secrets. Signed material comes from a server boundary, while the app submits transactions through the wallet or an explicit backend executor.
Integration Shape
App Responsibilities
- choose the market and manifest.
- collect user amount, direction, slippage, recipient, and deadline choices.
- call the quote server endpoint for the selected product path.
- pass returned signed payloads into the SDK execution helper for that path.
- surface reverted transactions with the SDK error helpers when possible.
Server Responsibilities
- hold signer keys or external signing custody.
- enforce supported market, token, amount, deadline, and inventory policy.
- reject mismatched product endpoints.
- return JSON that can be serialized without losing bigint precision.
Paths To Pick From
| Product path | Quote endpoint | Build page |
|---|---|---|
| Generic signed swap | POST /quote/sign | Quote Server Integration |
| Native stablecoin open | POST /quote/product/open | SDK Integration |
| Native stablecoin return | POST /quote/product/return | SDK Integration |
| Registered issuer swap | POST /quote/registered-issuer/sign | Registered Issuer Integration |
| Liquidation inventory | POST /quote/liquidations | Liquidation Bot Integration |
Keep Out Of The Browser
Do not expose private keys, JWTs, bearer tokens, solver credentials, or direct RPC credentials intended for privileged signing. Browser-safe configuration is limited to public chain, manifest, and address facts.
Source Files
interface/src/sdk/src/productSwapExecution.tssdk/src/productSwapPostState.tsquote-server/src/http.tsscript/testing/check-interface-secret-boundary.mjs