> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/core-api-reference/overview.md).

# Introduction

A detailed list of all Commerce Layer core resources

Commerce Layer is a flexible commerce API that features **400+ endpoints**. This is the detailed reference where you can explore the complete list of our core resources.

{% hint style="info" %}
Commerce Layer now supports explicit API versioning, and we just released a new version — see [API versioning](/core/api-versioning.md) to learn how it works. This reference documents the legacy `2017-08` version, still the default when no version is specified. We encourage you to start planning your move to the new `2026-05` version: the legacy version will now only be maintained on a bug-fix basis, while all new features — starting with the redesigned payments flow — are developed for the latest one exclusively.
{% endhint %}

{% hint style="warning" %}
The `2026-05` version itself is stable, but the resources it introduces — the redesigned payment flow in particular — are currently in **beta** and may still evolve as we refine them based on real-world usage. For now the [API reference](https://docs.commercelayer.io/core-api-reference/2026-05) is the only publicly available documentation for the new version. The related *Getting started* guide and *How-tos* are coming soon. In the meantime, they can be shared privately with teams who want to start checking or integrating against the new payments flow — reach out to us if you're interested.
{% endhint %}

## How it works

For each single resource you can find:

* The **resource** object and its fields, attributes, and relationships.
* The allowed **CRUD** operations you can perform on the related endpoint with basic examples of the request/response format.

## More to read

See our [Getting started](https://docs.commercelayer.io/core/) guide for basic information on how to [fetch](/core/fetching-resources.md), [create](/core/creating-resources.md), [update](/core/updating-resources.md) and [delete](/core/deleting-resources.md) resources or any other instruction you need to interact with our API.

Check our [changelog](https://docs.commercelayer.io/changelog/) to stay up-to-date with any changes we make on the APIs, apps, and open-source projects (including versioning, product releases, new features, and general improvements).

Read our [how-tos](https://docs.commercelayer.io/how-tos/) for step-by-step tutorials and best practices on how to handle the most common ecommerce scenarios.

Try out our [Metrics API](https://docs.commercelayer.io/metrics/) and see how it can enable you to gather and aggregate useful data that you can leverage to measure the health and performance of your ecommerce business.

Do you need to manage provisioning tasks programmatically, extend our Dashboard, or even build your own? Leverage our [Provisioning API](https://docs.commercelayer.io/provisioning/) and exercise greater control over your organizational structure and user roles.

Would you like to benefit from a DSL that enables you to define promotional rules? If you're an enterprise customer, you can ask to test our [Rules Engine](https://docs.commercelayer.io/rules-engine/) and start setting up almost any kind of [promotions](/core-api-reference/flex_promotions.md) to boost your sales, from the simplest to the most complex.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.commercelayer.io/core-api-reference/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.