# Asynchronous Operations

Some operations in our API are executed asynchronously, which means that you will not have to wait for the operation to finish.

In exchange, you will get a request ID that will allow you to consult the status of the operation via the call of another endpoint.

## Example of Response

This is an example of response from an asynchronous operation ([Manual IP Renew](/api/ip-rotation.md#execute-manual-rotation) in this case).

{% embed url="<https://gist.github.com/clintnetwork/a84acbfdb84e9a9aaee9864f04ebbb14>" %}
the field `requestId` in the `data` object can be used to retrieve the related operation.
{% endembed %}

## Retrieve an Operation with its ID

the field `requestId` in the `data` object can be used to retrieve the related operation

{% openapi src="/files/gs4oEIFDowGgQW6W05CO" path="/v2/Authentication/SignIn" method="post" %}
[swagger.json](https://3875752105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MdX5lpI2Fre91A5ipOw%2Fuploads%2FkaenjPxy480P6u3WD1PU%2Fswagger.json?alt=media\&token=d65d1f23-7d90-4149-af11-e3b4c609807e)
{% endopenapi %}

## Endpoints Using Asynchronous Operations

There is a lit of endpoints using asynchronous operations:

* Manual IP Renew
* Test


---

# 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.hypeproxy.io/basic-concepts/asynchronous-operations.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.