> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/api/docs.md).

# API Documentation

Reference documentation for using the Ango Hub API

<figure><picture><source srcset="https://angohub-docs-assets.s3.eu-central-1.amazonaws.com/cover/api_banner_dark.png" media="(prefers-color-scheme: dark)"><img src="https://angohub-docs-assets.s3.eu-central-1.amazonaws.com/cover/api_banner.png" alt=""></picture><figcaption></figcaption></figure>

The Ango Hub API provides programmatic access to the platform’s core functionality, allowing developers to integrate data annotation workflows directly into their own systems and pipelines.

Using the API, you can automate tasks such as project creation, asset management, label import and export, workflow operations, and user management without relying solely on the web interface.

This section documents the available API endpoints, their parameters, and expected responses. Each endpoint description includes request formats, required fields, and example usage to help you quickly integrate with the API.

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center">Overview</td><td><a href="/api/docs/overview.md">Overview</a></td></tr></tbody></table>

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center">Projects</td><td><a href="/api/docs/projects.md">Projects</a></td></tr><tr><td align="center">Tasks</td><td><a href="/api/docs/tasks.md">Tasks</a></td></tr><tr><td align="center">Assets</td><td><a href="/api/docs/assets.md">Assets</a></td></tr><tr><td align="center">Issues</td><td><a href="/api/docs/issues.md">Issues</a></td></tr><tr><td align="center">Storages</td><td><a href="/api/docs/storages.md">Storages</a></td></tr><tr><td align="center">Organization</td><td><a href="/api/docs/organization.md">Organization</a></td></tr><tr><td align="center">Import/Export</td><td><a href="/api/docs/import-export.md">Import/Export</a></td></tr><tr><td align="center">Batches</td><td><a href="/api/docs/batches.md">Batches</a></td></tr><tr><td align="center">Analytics</td><td><a href="/api/docs/analytics.md">Analytics</a></td></tr><tr><td align="center">Plugins</td><td><a href="/api/docs/plugins.md">Plugins</a></td></tr><tr><td align="center">Workflows</td><td><a href="/api/docs/workflows.md">Workflows</a></td></tr><tr><td align="center">Models</td><td><a href="/api/docs/models.md">Models</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.imerit.net/api/docs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
