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

# Arcware Cloud API Tokens

General Goal: To enable programmatic access and seamless integration between Arcware Cloud and external applications, automated workflows, or CI/CD pipelines using API token authentication.

### Arcware Cloud API Tokens

#### Availability

**API tokens are currently available upon request through Arcware Customer Support. Self-service token creation and management directly within the Arcware Cloud platform dashboard are planned for an upcoming release.**

#### API Documentation

Dedicated, centralized API documentation is currently in development. In the meantime, you can explore the available endpoints, request parameters, and response schemas via the interactive Swagger (OpenAPI) documentation provided for each core microservice:

* [Project Service](https://project-service.ragnarok.arcware.cloud/docs)
* [Instance Service](https://instance-service.ragnarok.arcware.cloud/docs)

{% hint style="warning" %}
Security Note: Not every endpoint listed in the interactive documentation is inherently available for API token access. Endpoint availability is strictly governed by the specific permissions and scope associated with your assigned token.
{% endhint %}


---

# 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.arcware.cloud/api/arcware-cloud-api-tokens.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.