API
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.
Base URL
All endpoints live under a versioned base URL:
https://api.snapvisor.io/v2OpenAPI specification
The full machine-readable specification (every endpoint, schema, and error shape) is published at:
https://api.snapvisor.io/v2/openapi.yamlImport it into your API client, code generator, or agent tooling. The Snapvisor MCP server exposes the same operations as MCP tools.
Authentication
Authenticate with a bearer token in the Authorization header:
- Personal access token — create one under Settings → Tokens in the app.
- OAuth access token — issued to applications and AI agents through the OAuth 2.1 flow described in the MCP server guide.
Project tokens (ARGOS_TOKEN) only upload builds from CI — they cannot call the REST API.
Typed client
For TypeScript projects, @snapvisor/api-client is a typed client for this API:
npm install @snapvisor/api-clientConnecting 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 MCP server guide.