Contentstack Content Delivery API

Name: Contentstack Content Delivery API
Brand: Contentstack Content Delivery API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey10 EndpointsREST

For Agents

Read published Contentstack content from a CDN: fetch content types, entries, global fields, taxonomies, and assets for the chosen environment.

Install Jentic One Beta

Connect the Contentstack Content Delivery API to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Contentstack Content Delivery API.

Fetch content type definitions including field schemas and references

Retrieve entries for a content type filtered by query, locale, and reference depth

Read global field definitions shared across content types

GET STARTED

Start building with Contentstack Content Delivery API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Contentstack Content Delivery API, keeping it validated and agent-ready. The Contentstack Content Delivery API is a read-only CDN-fronted API used to fetch published content into web and mobile properties, exposing content types, entries, global fields, taxonomies, assets, and a stack sync endpoint. Authentication uses a stack api_key and a delivery access_token in headers, with the environment supplied as a query parameter, and the API is available across North America, Europe, Azure North America, and Azure Europe regions.

Use Cases

Patterns agents use Contentstack Content Delivery API for, with concrete tasks.

★ Headless CMS-Powered Website

Front-end teams build a Next.js, Nuxt, or SvelteKit site that renders pages from Contentstack entries. The Content Delivery API returns published content from the regional CDN with low latency, and queries can include references and pick locale and environment for staging vs production. Integration is hours rather than days because the read API is small and stable.

GET /v3/content_types/blog_post/entries?environment=production&locale=en-us&include[]=author with the stack api_key and access_token to render a blog index page

Mobile App Content Sync

Mobile apps use the GET /v3/stacks/sync endpoint to download all published entries on first launch, persist a sync_token, and on subsequent launches retrieve only what has changed. This minimises bandwidth and battery use and lets the app function offline against the most recent published snapshot. Sync tokens expire if a stack is paused, so apps must handle a full re-init if a 422 is returned.

Call GET /v3/stacks/sync?init=true&environment=production with the stack credentials, persist the returned sync_token, and on the next call pass sync_token=<saved> to fetch only changes

Taxonomy-Driven Discovery Pages

Content sites use Contentstack taxonomies to power category and tag pages without hard-coding lists. GET /v3/taxonomies/entries returns the entries linked to a given taxonomy term, so navigation and filter UI can be generated from CMS data. This avoids building parallel tag systems in the front end.

GET /v3/taxonomies/entries?taxonomy_uid=topics&term_uid=ai&environment=production to render an AI-topic landing page

AI Agent Content Lookup via Jentic

An AI agent helping a content editor or chat support tool uses Jentic to fetch the latest published entry for a given uid or query a content type. The agent reads the schema, executes a GET, and returns structured fields without scraping the rendered site. Through Jentic the api_key and access_token live in MAXsystem so they never enter the agent's context.

Search Jentic for 'fetch a contentstack entry', execute with content_type_uid='product' and entry_uid='abc123' for environment=production, and return the entry JSON

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for contentstack content delivery api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v3/content_types

List content type definitions in the stack

GET

/v3/content_types/{content_type_uid}

Read a single content type schema

GET

/v3/content_types/{content_type_uid}/entries

List published entries for a content type

GET

/v3/content_types/{content_type_uid}/entries/{entry_uid}

Read a single entry by uid

GET

/v3/global_fields

List global field definitions

GET

/v3/assets

List published assets in the environment

GET

/v3/taxonomies/entries

List entries linked to taxonomy terms

GET

/v3/stacks/sync

Run an initial or delta content sync

GET

/v3/content_types

List content type definitions in the stack

GET

/v3/content_types/{content_type_uid}

Read a single content type schema

GET

/v3/content_types/{content_type_uid}/entries

List published entries for a content type

GET

/v3/content_types/{content_type_uid}/entries/{entry_uid}

Read a single entry by uid

GET

/v3/global_fields

List global field definitions

Why Jentic?

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

Credential isolation

The Contentstack stack api_key and delivery access_token are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access at call time and never see the raw delivery token, so the same agent can call multiple stacks or environments without leaking credentials between them.

Intent-based discovery

Agents search Jentic by intent (e.g. 'fetch a contentstack entry') and Jentic returns the matching CDA operation along with its input schema, including the environment query parameter, so the agent calls the right endpoint without browsing Contentstack's docs.

Time to first call

Direct Contentstack integration: 1-2 days to handle multi-region routing, locale selection, and reference depth parameters. Through Jentic: under an hour to search, load schema, and execute.

FAQs

Specific to using Contentstack Content Delivery API through Jentic.

Why is there no official OpenAPI spec for Contentstack Content Delivery API?

Contentstack publishes a Postman collection and a Swagger viewer but does not host a stable OpenAPI 3 file at a permanent URL. Jentic generates and maintains this spec so that AI agents and developers can call Contentstack Content Delivery API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Contentstack Content Delivery API use?

Each request must include the stack api_key header, the delivery access_token header, and an environment query parameter. Through Jentic the api_key and access_token are stored in the MAXsystem vault and supplied at call time, so the agent never holds the raw delivery token.

Can I read published entries with the Contentstack Content Delivery API?

Yes. GET /v3/content_types/{content_type_uid}/entries returns the published entries for a content type and GET /v3/content_types/{content_type_uid}/entries/{entry_uid} returns a single entry. Reference depth, locale, and field selection are controlled by query parameters.

What are the rate limits for the Contentstack Content Delivery API?

Contentstack applies per-stack and per-organisation rate limits to the Content Delivery API; current limits depend on the plan and are documented in the Contentstack rate-limit guide. Through Jentic, retries with exponential backoff are handled at the SDK level so transient 429 responses do not surface to agent code.

How do I run a content sync with the Contentstack Content Delivery API through Jentic?

Run `jentic.search('sync contentstack content')`, load the operation, and execute with init=true and environment=production. Jentic resolves this to GET /v3/stacks/sync and returns the sync_token to persist for the next delta call.

Does the Contentstack Content Delivery API support multiple regions?

Yes. The same spec is served from cdn.contentstack.io (NA), eu-cdn.contentstack.com (EU), azure-na-api.contentstack.com (Azure NA), and azure-eu-cda.contentstack.com (Azure EU). Pick the regional base URL that matches the stack's hosted region.