> ## Documentation Index
> Fetch the complete documentation index at: https://developer.jtl-software.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Available APIs

> The three APIs available for integrating with JTL, and how to choose between them.

The JTL Platform exposes three APIs for integrating with merchant data. They cover overlapping ground in different ways; the right choice depends on what you're building and where your integration runs.

## The Three APIs

Each API targets a different use case. Most integrations use one of the first two; SCX is specific to marketplace integrations.

| API                                                                  | What it's for                                                                                                                                                                           | Protocol       |
| -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
| [REST API](/api-reference/v2.0/accountingdata/query-accounting-data) | Transactional operations on merchant data (orders, items, customers, stock)                                                                                                             | REST over HTTP |
| [GraphQL API](/api-reference/graphql-playground)                     | Flexible queries over the same ERP domain, fetching exactly the fields you need                                                                                                         | GraphQL        |
| [SCX API](/api-reference/scx/channel)                                | OnPremise marketplace channel integrations (e.g., Amazon, eBay). See [Marketplace Channels](/guides/marketplace-channels/channel-api-overview) for channel-specific integration detail. | REST over HTTP |

## Common Conventions

Both ERP APIs target version `2.0` of the API and include authentication headers described in [Integration Overview](/guides/erp-integration/integration-overview#required-http-headers). They differ in pagination shape:

* **REST** uses page-based pagination with `pageNumber` and `pageSize` query parameters, returning a wrapped envelope with `items[]` and page metadata
* **GraphQL** uses cursor-based pagination with `first` and `after` variables, returning `nodes[]` and a `pageInfo` object

See [Pagination](/guides/essentials/common-patterns/pagination) for more details.

## Next Steps

<CardGroup cols={2}>
  <Card title="GraphQL Playground" icon="share-2" href="/api-reference/graphql-playground">
    Try queries and mutations interactively against your ERP instance.
  </Card>

  <Card title="REST API Reference" icon="code" href="/api-reference">
    Browse all REST API endpoints with request/response schemas.
  </Card>

  <Card title="Integration Overview" icon="plug" href="/guides/erp-integration/integration-overview">
    Base URLs, authentication, and required headers.
  </Card>

  <Card title="Pagination" icon="arrow-right" href="/guides/essentials/common-patterns/pagination">
    The full page-based pagination contract.
  </Card>
</CardGroup>