Prerequisites
- A dedicated Capture endpoint URL (provided by nexroute during onboarding)
- Source IPs allowlisted on that endpoint (coordinated during onboarding; see Authentication)
Methods
The endpoint speaks JSON-RPC 2.0 over HTTPS and WebSocket. Two submission methods are exposed:eth_sendPrivateRawTransaction— submit a single user-signed transaction. Use this for the common case where the user signs one swap and you forward it as-is.eth_sendBundle— submit an ordered list of user-signed transactions as an atomic bundle. Most useful when a swap needs its ERC-20 approval packed alongside it: pass[approval_tx, swap_tx]and the approval, swap, and backrun all land atomically. Mirrors Flashbots’eth_sendBundleshape.
-32601 method not found.
Submit a single transaction
tx, the hex-encoded raw signed transaction (0x-prefixed). The object shape mirrors Flashbots’ eth_sendPrivateTransaction and reserves room for optional fields (e.g. maxBlockNumber) without further wire breaks. 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).
Submit a bundle (approval + swap)
When the swap needs an ERC-20 approval the same user hasn’t issued yet, submit both transactions together so they land atomically with the backrun. Order matters: the last transaction is the source nexroute backruns behind; earlier transactions are dependencies bundled in front.result field contains the bundle hash (keccak256 of the concatenated transaction hashes).
Errors
Errors follow standard JSON-RPC conventions:
A non-error response means the submission has been accepted into the routing pipeline. Subsequent inclusion is monitored automatically.
Next steps
- Authentication: IP allowlist setup and operational notes
- Security: what nexroute guarantees about your orderflow
- eth_sendPrivateRawTransaction and eth_sendBundle: full method specifications