Plan your integration
A practical path from your first technical discussion to a validated rollout.
Start by establishing which transaction flow you want to route, which networks you need and how your application currently handles submission and confirmation.
1. Define your transaction flow
Describe your platform type, the point at which transactions are signed, your current submission route and the networks you need. Aggregate volume estimates and timing expectations help scope the discussion; do not include signing keys or credentials.
- Platform: wallet, trading platform or Telegram bot.
- Routing: where signed transactions are submitted today, including any parallel or fallback routes.
- Traffic: typical volume, peak concurrency and transaction types.
- Experience: how users see pending, confirmed, failed and expired transactions.
2. Agree on the connection
Book a technical discussion ↗. Confirm the exact network and environment, access method, request format and operational contact. Start with authentication, then submit a signed transaction and query its status using the Preview API contract.
Agree on the revenue calculation basis, applicable costs, attribution and settlement terms at the same time. The headline share is 60%; the details of accounting must be clear before traffic goes live.
3. Validate the complete lifecycle
Use the environment and test approach agreed with the team. Check successful submissions as well as invalid inputs, timeouts, duplicate submissions and transactions that do not land on-chain. Verify what a submission acknowledgment means before using it to update a user’s transaction status.
The integration checklist covers acceptance criteria. The transaction lifecycle explains why submission, inclusion and settlement must be tracked separately.
4. Prepare the rollout
Agree on an initial traffic scope, owners, monitoring and rollback criteria. Review how your application responds when the route is unavailable, including whether an alternative route would expose a transaction publicly. Expand only after the agreed validation criteria are met.
Bring an integration brief
Copy this template into your technical discussion notes.
Platform and technical owner:
Target network(s) and environment:
Current signing and submission flow:
Expected volume and peak concurrency:
Timing and confirmation requirements:
Existing retry, nonce and fallback behavior:
Monitoring and support contacts:
Revenue attribution and settlement questions: