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

# List of API endpoints

This page explains where to find the up-to-date list of Dastra API endpoints and how to read it.

## Browse the reference

The list of endpoints is generated from the API itself and published in the OpenAPI format:

* the Swagger interface: <https://api.dastra.eu/swagger/index.html>. It shows the parameters, data models and response codes of each endpoint, and lets you try a call once you have entered your key with the **Authorize** button;
* the OpenAPI definition in JSON: <https://api.dastra.eu/api/v1/dastra.json>, to generate a client in your language;
* the API reference: <https://dastra.readme.io>.

Only the public endpoints of the API are listed there. The compliance module (frameworks, controls, tests, audits) has its own reference, whose routes start with `/v1/compliance/ws/{workspaceId}/`: <https://api.dastra.eu/v1/compliance/swagger/index.html>.

## Read a path

A path starts with the API version and, for a workspace, with its identifier:

| Path                                       | Use                                      |
| ------------------------------------------ | ---------------------------------------- |
| `/v1/ws/{workspaceId}/Actors`              | The stakeholders of a workspace          |
| `/v1/ws/{workspaceId}/DataSubjectRequests` | The data subject requests of a workspace |
| `/v1/ws/{workspaceId}/Tags`                | The tags of a workspace                  |
| `/v1/Workspaces`                           | The workspaces of the organization       |

The HTTP method tells the action: `GET` reads, `POST` creates, `PUT` or `PATCH` modifies and `DELETE` deletes. Depending on the resource, additional routes exist, such as `/batch-delete` to delete several items or `/export/{format}` to export a list.

To check that an API key works, call `GET https://api.dastra.eu/me`.

For authentication, see [Authentication](https://doc.dastra.eu/en/api/authentication.md). For request limits, custom fields and tags, see [Configuration](https://doc.dastra.eu/en/api/configuration.md). For example calls, see [API use cases](https://doc.dastra.eu/en/api/use-cases.md).


---

# 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://doc.dastra.eu/en/api/endpoints.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.
