> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adside.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Access

> Call the API with a personal API key, or let the CLI call it for you.

This reference shows every public operation, with its inputs and outputs. You can call it in two ways:

* **From your own code**, with a personal API key sent as a bearer token. Create one in Adside, in **Settings**, then **API keys**. See [Sign-in and API keys](https://docs.adside.ai/authentication.md).
* **With the [CLI](https://docs.adside.ai/cli/install.md)**, which signs in for you and runs each operation as a command.

```bash theme={null}
curl https://api.adside.ai/v1/me \
  -H "Authorization: Bearer $ADSIDE_API_KEY"
```

Each page names the CLI command that runs it:

| On this page | CLI |
| - | - |
| `GET /v1/workspaces/{workspaceId}/assets` | `adside assets list` |

## How the API is laid out

The base URL is `https://api.adside.ai`. Operations sit under the thing they belong to:

* `/v1/workspaces/{workspaceId}/...` for a workspace
* `/v1/organizations/{organizationId}/...` for an organization

Every operation acts with the [permissions](https://docs.adside.ai/workspaces-and-permissions.md) of the person the key or login belongs to, and makes its change on the first call, with no [confirmation](https://docs.adside.ai/confirmations.md#the-cli-and-the-api) step. Through the API and the CLI, operations on ad platforms only read for now. Changing campaigns goes through the [MCP](https://docs.adside.ai/mcp/capabilities.md), behind a confirmation.

## Stable and beta operations

A stable operation keeps working: renaming or removing it comes with a deprecation window. A beta operation may still change.

Questions? Write to [support@adside.ai](mailto:support@adside.ai).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.