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

# Catalog, Customers & Access

> Products, subscription records, customers, and entitlements.

The generated endpoint pages contain the exact filters and response schemas for these Merchant API operations.

## Products

<CardGroup cols={2}>
  <Card title="List products" icon="list" href="/api-reference/endpoint/products">
    Search and filter the organization catalog.
  </Card>

  <Card title="Get a product" icon="box" href="/api-reference/endpoint/get-product">
    Read one product by its Anyway ID.
  </Card>

  <Card title="Get product payment links" icon="link" href="/api-reference/endpoint/get-product-payment-links">
    List the customer-facing Anyway links configured for a product.
  </Card>
</CardGroup>

## Subscription records

<CardGroup cols={2}>
  <Card title="List subscriptions" icon="list" href="/api-reference/endpoint/list-subscriptions">
    Filter and paginate recorded subscriptions.
  </Card>

  <Card title="Get a subscription" icon="calendar" href="/api-reference/endpoint/get-subscription">
    Inspect lifecycle, customer, product, and billing data.
  </Card>
</CardGroup>

Use these operations to inspect subscription records and their lifecycle data.

The list accepts `status` and `customer_id`. A subscription response includes its stable
`subscriptionId`, customer and product, `DAY`, `MONTH`, or `YEAR` billing interval,
current period end, scheduled-cancellation state, and initial/latest order IDs when those
relationships exist. These Merchant API operations are read-only; schedule cancellation
from the authenticated Business app.

## Customers

<CardGroup cols={2}>
  <Card title="List customers" icon="users" href="/api-reference/endpoint/list-customers">
    Read customers derived from commerce records.
  </Card>

  <Card title="Get a customer" icon="user" href="/api-reference/endpoint/get-customer">
    Inspect one derived customer identity.
  </Card>
</CardGroup>

Customers are derived from the organization's order history. A customer record contains
its stable `customerId` and normalized email. To load related commerce records, filter
orders and subscriptions with that `customer_id`.

## Entitlements

<Card title="Check entitlement" icon="badge-check" href="/api-reference/endpoint/check-entitlement">
  Resolve access using an email, wallet, or customer identity, optionally scoped to a product.
</Card>

An entitlement response describes current access; it is not a substitute for authenticating the person making the request. Match the resolved identity to your own authenticated user before granting content or service access.