# API reference

Canonical: https://snapvisor.io/docs/api-reference

> The Snapvisor REST API - base URL, authentication with personal access tokens or OAuth, and the full OpenAPI specification.



Everything in Snapvisor — builds, screenshots, diffs, reviews, comments — is available over a REST API described by an OpenAPI specification. Every operation in that specification has its own page in this section.

<Callout type="warn">
  Connecting an AI agent (Claude Code, Cursor, any MCP client)? Do NOT point it at this REST base URL — the MCP endpoint is `https://mcp.snapvisor.io`. See the [MCP server guide](/agents/mcp-server).
</Callout>

## Base URL [#base-url]

All endpoints live under a versioned base URL:

```text
https://api.snapvisor.io/v2
```

## OpenAPI specification [#openapi-specification]

The full machine-readable specification (every endpoint, schema, and error shape) is published at:

```text
https://api.snapvisor.io/v2/openapi.yaml
```

Import it into your API client, code generator, or agent tooling. The Snapvisor [MCP server](/agents/mcp-server) exposes the same operations as MCP tools.

## Authentication [#authentication]

Authenticate with a bearer token in the `Authorization` header:

* **Personal access token** — create one under Settings → Tokens. See [Access tokens](/tokens).
* **OAuth access token** — issued to applications and AI agents through the OAuth flow described in the [MCP server guide](/agents/mcp-server).

<Callout type="warn">
  Project tokens (`ARGOS_TOKEN`) only upload builds from CI — they cannot call the REST API.
</Callout>

