This guide walks an onboarded partner through their first submission.Documentation Index
Fetch the complete documentation index at: https://docs.nexroute.io/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A dedicated Capture endpoint URL (provided by nexroute during onboarding)
- Source IPs allowlisted on that endpoint (coordinated during onboarding; see Authentication)
Submit a transaction
The endpoint speaks JSON-RPC 2.0 over HTTPS and WebSocket. The only supported method iseth_sendRawTransaction; any other method returns -32601 method not found.
0x-prefixed). The signature is the user’s; nexroute does not modify the payload.
Response
The endpoint returns a JSON-RPC envelope echoing the requestid. The result field contains the transaction hash (0x-prefixed, 32 bytes).
Errors
Errors follow standard JSON-RPC conventions:| Code | Cause |
|---|---|
-32601 | Method other than eth_sendRawTransaction |
-32000 | Malformed transaction (RLP decode failure, invalid signature) |
-32603 | Internal error during forwarding (rare; nexroute always retries before surfacing) |
Health check
A simple liveness probe is exposed atGET /health:
Next steps
- Authentication: IP allowlist setup and operational notes
- Security: what nexroute guarantees about your orderflow
- API reference: complete method specification