> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/interfaces/apis/core-apis.md).

# Core APIs

Reference for platform-api: tenant apps and links, log search, workload metrics, and user tokens.

Product-facing reference for `platform-api`, the gateway that exposes tenant resource listings, log search, observability metrics, user token management, and other platform-level operations. Paths in this section are relative to `https://<DATAOS_FQDN>/platform-api`; see [Authentication](https://v2.dataos.info/references/interfaces/apis/core-apis/authentication.md) for the full base URL.

### What you can do

<table><thead><tr><th width="158.830078125">Capability</th><th>What it covers</th></tr></thead><tbody><tr><td><strong>Tenant resources</strong></td><td>List apps and links registered for a tenant, with product-based filtering.</td></tr><tr><td><strong>Log search</strong></td><td>Search logs for a specific tenant resource, grouped by pod/container.</td></tr><tr><td><strong>Observability metrics</strong></td><td>Query workload metrics from Instance Prometheus with PromQL, as instant or range queries.</td></tr><tr><td><strong>User tokens</strong></td><td>Create, list, retrieve, and delete a user's API tokens for automated provisioning.</td></tr></tbody></table>

### Start here

* [Authentication](https://v2.dataos.info/references/interfaces/apis/core-apis/authentication.md): Use a Bearer token or an `apikey` header, plus optional tracing headers.
* [API Reference](https://v2.dataos.info/references/interfaces/apis/core-apis/api-reference.md) : Find endpoint groups and detailed request/response behavior.


---

# 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://v2.dataos.info/references/interfaces/apis/core-apis.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.
