# 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 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 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: "Request is currently being processed."
* **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; the request 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.staking.galaxy.com/ethereum/client-request-identifier.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.