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

# Atreemo API reference

Full-fidelity OpenAPI reference for the direct Atreemo API

{% hint style="warning" %}
**Beta, runtime validation pending.** The reference describes 217 operations on 212 paths. Its source is public API version 1.34.0.0 / Release1.34; runtime compatibility with the current non-production Release1.35 environment remains to be validated.
{% endhint %}

The full-fidelity OpenAPI 3.0.3 contract is held in the private GitBook OpenAPI source `atreemo-api`. It preserves native parameter names, recursive source schemas, evidence extensions, four truthful bodyless success responses, open dynamic `DataTable` rows and the canonical GET request body for `WorkspaceInviteUser`.

The private GitBook OpenAPI source lists Production and Staging as the only developer-facing resource servers:

```
Production
https://api.hos.accessacloud.com/atreemo-api

Staging
https://api-staging.hos.accessacloud.com/atreemo-api
```

Interactive requests are disabled in this reference. Endpoint availability and routing behaviour require staged release validation; use Staging for integration validation.


---

# 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.hos.accessacloud.com/atreemo-api/api-reference/atreemo-api-reference.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.