> For the complete documentation index, see [llms.txt](https://developer.cloudfactory.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.cloudfactory.com/cloudfactory-public-api/reference/human-oversight-api.md).

# Oversight

<figure><img src="/files/PdTMyIi5CyxJ071QN2z0" alt=""><figcaption></figcaption></figure>

### Oversight API Workflow

This workflow describes the process of uploading a media asset and creating a task request.

***NOTE**: Skip **Step 1** and **Step 2** if using Mounted Buckets* Mounted buckets currently only support image assets. For video assets, please use **Step 1** and **Step 2**.

#### Step 1: Upload Media ( Not needed if using Mounted Buckets )

1. Use the Upload Media API to initiate the upload process.
2. Provide:
   * configuration\_id: This should have been passed to you.
3. The API returns a response containing:
   * media\_upload\_url: URL for uploading the actual media content.
   * media\_key: Unique identifier associated with the uploaded media.

#### Step 2: Upload Media Data ( Not needed if using Mounted Buckets )

1. Prepare the media file for upload.
2. Use the media\_upload\_url from the previous step to make a PUT request with the media data.
3. Choose Binary type in body and upload your media file.
4. Ensure the proper content-type is set for your media file in the request header. [Read More](/getting-started/upload-media.md)

#### Step 3: Create Task Request

1. Use the Create Task API to create a request.
2. Provide:
   * media\_key: The media key obtained in Step 1.
   * (Optional) bucket\_id: Provide the bucket credential Id , if using Mounted Buckets.
   * configuration\_id: The same ID used for media upload.
   * (Optional) callback\_url: URL for receiving notifications about task completion.
3. The API returns a response containing:
   * task\_id: Unique identifier for the created task request.

### Success:

* The media is uploaded to CloudFactory.
* A task is created and media is available in hasty project ready for annotation.

You can use the task\_id to track the progress or retrieve results

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><strong>Submit Task</strong></td><td></td><td><a href="/pages/fwlZzfeG472M5b6ALDVj">/pages/fwlZzfeG472M5b6ALDVj</a></td></tr><tr><td></td><td><strong>Upload Media</strong></td><td></td><td><a href="/pages/yQ6BBZfpc4OHA9ujvsVU">/pages/yQ6BBZfpc4OHA9ujvsVU</a></td></tr><tr><td></td><td><strong>Task Status</strong></td><td></td><td><a href="/pages/pxSxL0exHtR8q1bX9anw">/pages/pxSxL0exHtR8q1bX9anw</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://developer.cloudfactory.com/cloudfactory-public-api/reference/human-oversight-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.