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

# Developer overview

> Integrate with the Solya REST API — authentication, conventions, and where to find the full reference.

The Solya REST API exposes the platform's capabilities — catalog browsing, inventory
plans, analytics, alerts, tags, workflows, and data-platform operations — to external
programs, scripts, and AI agents.

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/en/developers/authentication">
    The three auth schemes and how to create and use a service-account token.
  </Card>

  <Card title="Making requests" icon="paper-plane" href="/en/developers/making-requests">
    Base URL, pagination, filtering, and introspecting your token.
  </Card>

  <Card title="Error codes" icon="circle-exclamation" href="/en/developers/error-codes">
    Response envelope, error codes, and HTTP status mapping.
  </Card>

  <Card title="API Reference" icon="code">
    The full, always-up-to-date endpoint reference — open the **API Reference** tab.
  </Card>

  <Card title="MCP gateway" icon="plug" href="/en/mcp/overview">
    Drive Solya from an AI agent (Claude, Cursor) via the Model Context Protocol.
  </Card>
</CardGroup>

## Conventions at a glance

* **Base URL** — `https://app.solya.app` (production). Endpoints live under `/api/`.
* **Format** — JSON request and response bodies.
* **Auth** — send `Authorization: Bearer <token>`. See
  [Authentication](/en/developers/authentication).
* **Tenancy** — every token and session is scoped to one **organization**; you only ever
  read or write that organization's data.
* **Responses** — a consistent envelope with a `success` flag and, on failure, a stable
  `errorCode` you can branch on. See [Error codes](/en/developers/error-codes).

<Note>
  The **API Reference** tab is generated directly from Solya's OpenAPI specification, so
  it always matches the running API. This Developers section adds the cross-cutting
  concepts the per-endpoint reference doesn't repeat.
</Note>