VTEX Headless CMS

Name: VTEX Headless CMS API
Brand: VTEX Headless CMS
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent Managementnone3 EndpointsREST

For Agents

Programmatically get all content types, get all cms pages by content type. Covers 3 operations.

Use for: I need to all content types, I want to all cms pages by content type, Search for cms page, List all records from VTEX Headless CMS

Connect the VTEX Headless CMS to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the VTEX Headless CMS, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with VTEX Headless CMS API.

Get all content types

Manage marketing data programmatically

Integrate VTEX Headless CMS into automated workflows

Query and filter VTEX Headless CMS records by parameters

GET STARTED

Start building with VTEX Headless CMS API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for VTEX Headless CMS, keeping it validated and agent-ready.

The [VTEX Headless CMS](https://www.faststore.dev/docs/headless-cms-overview) is a solution for storefront content management. You can use the Headless CMS API to fetch data about your project's pages and content types, including `status`, `id`, and `type`. Index Pages - `GET` [Get all Content Types](https://developers.vtex.com/docs/api-reference/headless-cms-api#get-/_v/cms/api/-projectId-) - `GE. The API exposes 3 endpoints.

Use Cases

Patterns agents use VTEX Headless CMS API for, with concrete tasks.

★ Marketing Operations

Use the VTEX Headless CMS to perform marketing operations programmatically. The API provides 3 endpoints covering core functionality including get all content types, get all cms pages by content type, get cms page.

Call GET /_v/cms/api/{projectId} to get all content types

Automated Pages Management

Automate pages operations by combining multiple VTEX Headless CMS endpoints. Agents can get all cms pages by content type and then get cms page in a single workflow.

Call GET /_v/cms/api/{projectId}/{content-type} to get all cms pages by content type, then verify the result

AI Agent Integration via Jentic

AI agents discover and call VTEX Headless CMS endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for 'get all content types', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — the [vtex headless cms](https://www.

METHOD

PATH

DESCRIPTION

GET

/_v/cms/api/{projectId}

Get all content types

GET

/_v/cms/api/{projectId}/{content-type}

Get all CMS pages by content type

GET

/_v/cms/api/{projectId}/{content-type}/{document-id}

Get CMS page

GET

/_v/cms/api/{projectId}

Get all content types

GET

/_v/cms/api/{projectId}/{content-type}

Get all CMS pages by content type

GET

/_v/cms/api/{projectId}/{content-type}/{document-id}

Get CMS page

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

VTEX Headless CMS none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get all content types') and Jentic returns the matching VTEX Headless CMS operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct VTEX Headless CMS integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mailchimp

Alternative marketing API

Choose Mailchimp when you need a different approach to marketing operations

Alternative

Hubspot

Alternative marketing API

Choose Hubspot when you need a different approach to marketing operations

FAQs

Specific to using VTEX Headless CMS API through Jentic.

What authentication does the VTEX Headless CMS use?

The VTEX Headless CMS uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get all content types with the VTEX Headless CMS?

Yes. Use the GET /_v/cms/api/{projectId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the VTEX Headless CMS?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get all content types through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get all content types'. Jentic returns the matching VTEX Headless CMS operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the VTEX Headless CMS have?

The VTEX Headless CMS exposes 3 endpoints covering pages operations.