# Auth

The Azure Dev API uses API Access Keys for a workspace.

Each access key is bound to a given workspace and only has access to resources inside of that workspace. As such, if your API integration needs resources from multiple workspaces, then an API key will need to be created per workspace.

### Creating a new API Access Key

An API key can be created via logging into the [PMS application](https://pms.lavanda.app/), and select the workspace to integrate against, then navigate to Settings -> Developer.

On this screen click the "Generate New Key" button.

This will issue you an API Access Key that can be used in the Azure Dev API.

### Key Permissions & Scopes

Each API Key has defined scopes for what resources it is permitted to.

<figure><img src="https://2517006499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQPvCHCc2jMrJC6Zfglq0%2Fuploads%2Fgit-blob-1b44acd157f10241be162959d6b65c01ebf7e7ea%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lavanda.app/legacy/auth.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.