> ## 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.

# Business API Reference

> Connect a merchant backend to Anyway's public commerce API and webhook contracts.

Use the public Merchant API when your backend needs to read commerce records, confirm order and payment status, or automate fulfillment. The Business app remains the place to create API keys, configure webhook endpoints, manage products, and operate Finance.

<Info>
  Endpoint pages are generated from the published OpenAPI contract. Use those pages as the source of truth for paths, parameters, response fields, and status codes.
</Info>

<Card title="Open the complete API Reference" icon="arrow-up-right-from-square" href="/api-reference/introduction">
  Choose the correct public API surface, credential, and integration contract.
</Card>

## Business integration paths

<CardGroup cols={2}>
  <Card title="Merchant API" icon="store" href="/api-reference/merchant-api">
    Understand the organization-scoped, server-side commerce API.
  </Card>

  <Card title="Authentication" icon="key" href="/api-reference/authentication">
    Create and use a Merchant API key without exposing it to browser code.
  </Card>

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

  <Card title="Products and access" icon="boxes-stacked" href="/api-reference/catalog">
    Work with products, subscriptions, customers, and entitlements.
  </Card>

  <Card title="Payment webhooks" icon="webhook" href="/api-reference/endpoint/webhooks">
    Verify signed events and process retries safely.
  </Card>

  <Card title="Choose the right API" icon="diagram-project" href="/api-reference/api-surfaces">
    Distinguish Merchant API, webhooks, agent runtime, SuperAPI, and telemetry.
  </Card>
</CardGroup>

<Warning>
  Use only the customer-facing contracts linked from this page. Undocumented services and routes are not public integration surfaces.
</Warning>