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

# Merchant API

> Access commerce resources using a server-side Merchant API key.

The Merchant API is the stable, organization-scoped commerce API for merchant backends. Its endpoint pages are rendered from the published OpenAPI contract, so request parameters and response schemas stay aligned with the running service.

<Note>
  Use the generated endpoint pages as the source of truth for paths, parameters, fields, and status codes. These guides explain how to use the API without duplicating the contract.
</Note>

## Explore the API

<CardGroup cols={2}>
  <Card title="API key information" icon="key" href="/api-reference/endpoint/api-keys">
    Inspect the organization and key associated with the current request.
  </Card>

  <Card title="Orders" icon="receipt" href="/api-reference/orders-guide">
    Confirm payment status and build idempotent fulfillment.
  </Card>

  <Card title="Catalog & access" icon="boxes-stacked" href="/api-reference/catalog">
    Access products, subscriptions, customers, and entitlements.
  </Card>

  <Card title="Generated schema" icon="brackets-curly" href="/api-reference/endpoint/orders">
    Inspect exact query parameters, response fields, and errors.
  </Card>
</CardGroup>

## Common rules

* The public Merchant API uses a server-side `X-API-Key`.
* Every request is scoped to the organization associated with that key.
* Successful responses use the standard response envelope; list operations return paginated data.
* A missing or invalid key is rejected before organization data is resolved.

<Warning>
  Never expose a Merchant API key in browser code, a mobile application, a public repository, or a customer-visible URL.
</Warning>