Kontent.ai Delivery API
★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey8 EndpointsREST
For Agents
Fetch published headless CMS content from Kontent.ai — content items, types, languages, and taxonomies — for an environment, ready to render on a site or app.
Use for: Get the latest blog content items from my Kontent.ai project, List all content types defined in my Kontent.ai environment, Retrieve a content item by codename for a specific language, Find all available languages configured in Kontent.ai
Not supported: Does not handle content authoring, asset uploads, or workflow management — use for delivery of published content only.
Jentic publishes the only available OpenAPI specification for Kontent.ai Delivery API, keeping it validated and agent-ready. The Kontent.ai Delivery API is a read-only REST interface to the Kontent.ai headless CMS that returns published content items, content types, languages, and taxonomy groups from a project environment. Responses are JSON and can be filtered, ordered, and paginated to drive websites, apps, and channel-specific renderers from a single content source. Authentication is by API key passed in the request header, and content is scoped per environment so that production and preview content stay isolated.
Install Jentic One Beta
Connect the Kontent.ai Delivery API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kontent.ai 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.
1
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 | sh2
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 instanceJentic 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 Kontent.ai Delivery API.
Retrieve published content items by codename or filter expression for a given environment
List the content types defined in a project to drive dynamic schema-aware rendering
Inspect element definitions on a content type to map editor fields to UI components
Enumerate active project languages to power locale-aware content fetching
Browse taxonomy groups and terms to support faceted navigation and tagging
Filter, order, and paginate content item collections to deliver listing pages efficiently
Use Cases
Patterns agents use Kontent.ai Delivery API for, with concrete tasks.
★ Headless website content delivery
Power a marketing website or single-page app by fetching published Kontent.ai content items by type and language, then rendering them through a frontend framework. The Delivery API returns versioned JSON for items, types, and taxonomies so editors can publish from Kontent.ai while the site updates without a redeploy. A typical Jamstack integration takes a day to wire up listing and detail pages against /items and /items/{codename}.
Fetch the first 20 published items of type 'article' in language 'en-US' from /items and return their codenames and titles.
Localized content rendering
Serve content in multiple languages from a single Kontent.ai project by enumerating configured languages via /languages and requesting items with a language parameter. Editors maintain translations in the CMS while the application picks the correct variant per user locale. This pattern is used by content teams shipping in 5-30 languages without duplicating the content tree.
Call /languages to list configured locales, then fetch /items/homepage with the language code 'fr-FR' and return the rendered fields.
Taxonomy-driven navigation
Build category and tag-based navigation by reading taxonomy groups from /taxonomies and matching content items by their taxonomy element values. Editors curate the taxonomy in Kontent.ai and the front end uses it to render filter facets, related content lists, and section pages. Implementation typically takes a few hours once the content model is finalised.
Get the 'topics' taxonomy group from /taxonomies/topics and list all terms with their codenames.
Agent-driven content retrieval via Jentic
An AI agent searches Jentic for 'fetch published content items' and receives the Kontent.ai Delivery API operation with its input schema. The agent supplies the environment ID and content type, executes the call through Jentic, and receives structured JSON without needing to read Kontent.ai documentation or handle the API key directly — Jentic keeps the key in MAXsystem and injects it at runtime.
Use the Jentic MCP tool kontent_list_items to fetch the latest 5 items of type 'product' and summarise their fields.
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for kontent.
METHOD
PATH
DESCRIPTION
GET
/items
List content items
GET
/items/{codename}
Get a single content item
GET
/types
List content types
GET
/types/{codename}/elements/{element_codename}
Get a content type element
GET
/languages
List configured languages
GET
/taxonomies
List taxonomy groups
GET
/items
List content items
GET
/items/{codename}
Get a single content item
GET
/types
List content types
GET
/types/{codename}/elements/{element_codename}
Get a content type element
GET
/languages
List configured languages
GET
/taxonomies
List taxonomy groups
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Kontent.ai Delivery API key is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access — the raw key is injected at request time and never enters the agent's context window.
Intent-based discovery
Agents search Jentic by intent (e.g. 'fetch published content items') and Jentic returns the matching Kontent.ai Delivery operations with their input schemas, so the agent can call /items or /types without browsing docs.
Time to first call
Direct Kontent.ai integration: a few hours for auth, environment scoping, and pagination. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Kontent.ai Delivery API through Jentic.
Why is there no official OpenAPI spec for Kontent.ai Delivery API?
Kontent.ai does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kontent.ai 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 Kontent.ai Delivery API use?
The Delivery API uses an API key passed in the request header (apiKeyAuth scheme). Jentic stores this key encrypted in MAXsystem and injects it per request — the agent never sees the raw key in its context.
Can I fetch content in a specific language with the Kontent.ai Delivery API?
Yes. Call GET /languages to list locales configured for the environment, then pass the language codename when requesting /items or /items/{codename} to receive that language variant.
What are the rate limits for the Kontent.ai Delivery API?
Kontent.ai applies rate limits at the project and CDN tier rather than per endpoint, with the exact ceiling depending on your subscription. Cache responses where possible and use the published content cache hints returned in response headers.
How do I list all content types through Jentic?
Search Jentic for 'list content types kontent' and load the GET /types operation. Execute it with your environment_id and the call returns all types and their element definitions in a single JSON response.
Does the Delivery API support content management operations?
No. The Delivery API is read-only for published content. Creating, updating, or unpublishing content uses the separate Kontent.ai Management API, which is not covered by this spec.
GET STARTED