Client Request Identifier

The "client_req_id" parameter in the request payload serves as a unique identifier for each request. In the event that the client's connection with the BlueShift Staking API Gateway is interrupted, the client is expected to capture the disconnection event and re-invoke the endpoint with the same payload. Upon receiving such a request, the BlueShift platform checks for the presence of the client_req_id and takes the following actions:

• Ongoing Processing: If the client_req_id exists and is associated with an active client session, but the request is still being processed, the response will be returned once processing is complete. Any new request with the same client_req_id will receive an HTTP 400 response with the message: "Duplicate client request. <client_req_id> is associated with an active client session."

• Processing Complete, Response Not Dispatched: If the client_req_id exists and the request was successfully processed, but the response was not dispatched (possibly due to a dropped client session), the new request will receive the undispatched response with an HTTP 200 status.

• Request Already Served: If the client_req_id exists but the response was already returned, the client will receive an HTTP 400 response with the message: "Duplicate client request. <client_req_id> has already been served."

• New Request: If the client_req_id does not exist in the platform, the request will be treated as new, processed, and responded accordingly.