> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/kentico-kontent.md).
# Kentico Kontent
Set up the Kentico Kontent connector in Pandium using basic authentication so tenants can securely sync headless CMS content across channels with project ID and API keys.
## **Connector Overview**
Kontent by Kentico is a headless CMS platform that allows businesses to manage and deliver content to multiple channels through an API-driven approach.
## **Authentication Type**
Basic
## **Webhook Supported**
No
## **Secrets**
* PAN\_SEC\_KENTICO\_KONTENT\_PROJECT\_ID
* PAN\_SEC\_KENTICO\_KONTENT\_MANAGEMENT\_API\_KEY
* PAN\_SEC\_KENTICO\_KONTENT\_DELIVERY\_API\_KEY\_NEEDED\_IF\_SECURED\_
* PAN\_SEC\_KENTICO\_KONTENT\_PREVIEW\_API\_KEY
## **API Client Supported**
No
## **Requirements for Provisioning**
In order to provision your connector, the following Kontent information must be gathered:
* Project ID
* Management API Key
* Delivery API Key (Needed if "Secured")
* Preview API Key
## **API Resources**
For more information on how to utilize the Kontent API, feel free to reference the following [documentation](https://kontent.ai/learn/docs/apis/openapi/delivery-api/).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pandium.com/connectors/connectors-101/kentico-kontent.md?ask=&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 `automate deployments from our CI pipeline` 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.
