# Public API endpoints

Commerce Layer exposes several public API endpoints that don't require authentication. Use these to query available resources, validate carrier accounts and rule schemas, check organization configurations, or download OpenAPI specifications for client library generation and API validation — all before requesting your first API token.

## Core API

Access public endpoints for [Core API](https://docs.commercelayer.io/core-api-reference/) resources, carrier configurations, and OpenAPI specifications. These unauthenticated endpoints help you discover the data model, validate shipping integrations, and generate client libraries without requiring API credentials.

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h4><i class="fa-list-tree">:list-tree:</i></h4></td><td><strong>API resources</strong></td><td>Query all available Core API resources and their endpoints. Useful for discovering the data model, understanding resource types, and building dynamic tooling without authentication.</td><td><a href="https://core.commercelayer.io/api/public/resources">https://core.commercelayer.io/api/public/resources</a></td><td></td></tr><tr><td><h4><i class="fa-radar">:radar:</i></h4></td><td><strong>OpenAPI schema</strong></td><td>Download the complete OpenAPI 3.0 specification for Core API. Generate client libraries, validate requests, and build development tooling with our machine-readable API definition.</td><td><a href="https://data.commercelayer.app/schemas/openapi.json">https://data.commercelayer.app/schemas/openapi.json</a></td><td></td></tr><tr><td><h4><i class="fa-truck">:truck:</i></h4></td><td><strong>Carrier accounts schema</strong></td><td>Get the JSON schema listing 100+ supported shipping carriers. Check required credentials, field labels, and configuration details for each carrier to set up shipping integrations correctly.</td><td><a href="https://core.commercelayer.io/api/public/schemas/carrier_accounts">https://core.commercelayer.io/api/public/schemas/carrier_accounts</a></td><td></td></tr></tbody></table>

## Rules Engine

Retrieve JSON schemas for building dynamic business rules across Commerce Layer using the [Rules Engine](https://docs.commercelayer.io/rules-engine/). These public endpoints provide the structure and validation requirements for order processing logic, pricing strategies, and conditional workflows — essential for creating flexible, rules-based commerce experiences.

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h4><i class="fa-cart-circle-check">:cart-circle-check:</i></h4></td><td><strong>Order rules schema</strong></td><td>Access the JSON schema for order rules used in flex promotions. Validate rule structures that check conditions against order payloads and apply actions like discounts and free shipping based on order attributes.</td><td><a href="https://core.commercelayer.io/api/public/schemas/order_rules">https://core.commercelayer.io/api/public/schemas/order_rules</a></td><td></td></tr><tr><td><h4><i class="fa-square-dollar">:square-dollar:</i></h4></td><td><strong>Price rules schema</strong></td><td>Access the JSON schema for price list rules. Validate rule structures that apply discounts to prices based on conditions like SKU codes, markets, or product attributes — perfect for market-specific pricing strategies.</td><td><a href="https://core.commercelayer.io/api/public/schemas/price_list_rules">https://core.commercelayer.io/api/public/schemas/price_list_rules</a></td><td></td></tr></tbody></table>

## Metrics API

Access the OpenAPI specification for [Metrics API](https://docs.commercelayer.io/metrics-api-reference/) to build analytics integrations and reporting tools. This public endpoint provides the complete API definition for querying commerce data, calculating KPIs, and building custom dashboards — no authentication needed for schema access.

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h4><i class="fa-radar">:radar:</i></h4></td><td><strong>OpenAPI schema</strong></td><td>Download the complete OpenAPI 3.0 specification for Metrics API. Build analytics integrations, validate query structures, and generate typed clients for commerce insights and reporting.</td><td><a href="https://data.commercelayer.app/schemas/metrics/openapi.json">https://data.commercelayer.app/schemas/metrics/openapi.json</a></td><td></td></tr></tbody></table>

## Provisioning API

Explore public endpoints for [Provisioning API](https://docs.commercelayer.io/provisioning/) resources and configuration schemas. Query available endpoints, validate organization settings and OAuth configurations without authentication — ideal for building onboarding tools, administrative integrations, and account management automation.

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><h4><i class="fa-list-tree">:list-tree:</i></h4></td><td><strong>API resources</strong></td><td>Query all available Provisioning API resources and endpoints. Discover organization management, team configuration, and access control capabilities without requiring authentication.</td><td><a href="https://provisioning.commercelayer.io/api/public/resources">https://provisioning.commercelayer.io/api/public/resources</a></td><td></td></tr><tr><td><h4><i class="fa-radar">:radar:</i></h4></td><td><strong>OpenAPI schema</strong></td><td>Download the complete OpenAPI 3.0 specification for Provisioning API. Generate SDKs, validate requests, and automate account management tooling with our full API definition.</td><td><a href="https://data.commercelayer.app/schemas/provisioning/openapi.json">https://data.commercelayer.app/schemas/provisioning/openapi.json</a></td><td></td></tr><tr><td><h4><i class="fa-gears">:gears:</i></h4></td><td><strong>Organization config schema</strong></td><td>Get the JSON schema for organization configuration settings. Validate micro frontend links, checkout options, app behaviors, API settings, and well-known metadata when customizing your org.</td><td><a href="https://provisioning.commercelayer.io/api/public/schemas/organization_config">https://provisioning.commercelayer.io/api/public/schemas/organization_config</a></td><td></td></tr><tr><td><h4><i class="fa-user-viewfinder">:user-viewfinder:</i></h4></td><td><strong>OAuth data schema</strong></td><td>Access the JSON schema for identity provider OAuth configurations. Validate SSO settings including client credentials, issuer URLs, JWKS endpoints, and domain scopes when setting up Single Sign-On.</td><td><a href="https://provisioning.commercelayer.io/api/public/schemas/oauth_data">https://provisioning.commercelayer.io/api/public/schemas/oauth_data</a></td><td></td></tr></tbody></table>


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.commercelayer.io/public-endpoints.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.