Submission Methods
Last updated
Last updated
Bundles can be submitted to the FastLane Relay RPC endpoint using JSON-RPC 2.0 over HTTPS and Websocket.
Searchers can send their submissions to the FastLane Relay API by calling the methods pfl_addSearcherBundle
for Bundles
More information on the FastLane Relay API and API calls can be found here:
Rate limits (for both HTTP and websocket):
Request/message limit per second: 2
Burst limit: 32
Repeatedly going over the rate limit will result in temporary IP ban, ranging from 3 minutes to 24 hours.
It's recommended that you use HTTP Keep-Alive connections to connect to the RPC endpoint to minimize TLS connection establishment times as it significantly reduces request latency when sending a bundle if the TLS handshake is already complete.
The /ping
endpoint is available for establishing a session, you can have a maximum of 2 sessions per IP address, and sessions will persist for a maximum of 15 minutes.
Example:
Ping
messages will be sent to your connection every 60 seconds. A pong
response must be sent to avoid disconnection. Alternatively, you can send ping
messages yourself to the server every minutes and get pong
responses.
To keep a websocket connection open and stable on a long term, we highly recommend to send ping
messages to the server every minutes, and to answer pong
every time the server sends a ping
message.
To better track responses (e.g. when sending multiple concurrent requests), it is highly advised to specify a unique id
for each new requests, see example below.
Example: