Access - Adside

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.
With the CLI, which signs in for you and runs each operation as a command.

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 of the person the key or login belongs to, and makes its change on the first call, with no confirmation step. Through the API and the CLI, operations on ad platforms only read for now. Changing campaigns goes through the MCP, 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.