# Asynchronous Endpoints

All long-running operations we offer through the API are exposed in an asynchronous manner. What this means is that these operations will generally require this query pattern on your part:

* Initiate the task, usually at a `/new` endpoint, which gives you a task id
* Query a nearby `/status` endpoint with that task ID to get the current status of the task. The statuses can be any of the following.
  * `SUBMITTED`: We have received your request but have not yet started working on it.
  * `IN_PROGRESS`: A worker is actively processing your request.
  * `SUCCEEDED`: Your request has been completed. A metadata field will be attached providing the location of the finished result, which you can generally issue a `GET` request to retrieve.
  * `FAILED`: Your request failed. A metadata field will be attached with a reason why, which can often be helpful in order to determine a fix and resubmit.

For a good example of an asynchronous endpoint, check out the [Chat Explore endpoint page](/akkio-docs/endpoints-and-schemas/endpoints/chat-explore.md).


---

# 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.akkio.com/akkio-docs/concepts/asynchronous-endpoints.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.