Download OpenAPI specification:Download
The Management API is a secure REST API that provides read and write access to your Kontent projects and subscriptions.
Use the API to import, update, or delete content in your Kontent project. When getting and updating content through the API, you always work with the latest versions of content, just like in the UI. The API cannot be used on published content unless you create new versions (in UI or via API) of the content items first.
Subscription admins on Enterprise plans with a Subscription API key can also use the Management API to manage users, roles, and projects under a subscription.
The base URL for all requests to the Management API is
- cURLcurl --request GET \ --url https://manage.kontent.ai/v2/projects/<YOUR_PROJECT_ID>/items \ --header 'Authorization: Bearer <YOUR_API_KEY>' \ --header 'x-continuation: <continuation_token>' \ --header 'Content-type: application/json'
Try out any of the Kontent APIs with Postman! 📫 The Postman collection is regularly updated and contains endpoints for all Kontent REST APIs, just like in the API references.
To work with the Management API, send your requests over HTTPS and authenticate using the
Authorization header in the following format:
Authorization: Bearer <YOUR_API_KEY>.
You can authenticate Management API v2 requests using one of two types of keys:
|Security Scheme Type||HTTP|
|HTTP Authorization Scheme||bearer|
|Bearer format||"Bearer <YOUR_API_KEY>"|
To get your API key for the Management API, go to Kontent > Project settings > API keys. The Management API accepts two kinds of API keys, Management API key and Subscription API key.
The state of the Management API may change in the future, however, the majority won't be breaking changes. To help you create more robust scripts and integrations, we've prepared a list of general changes to the API that we don't consider breaking. We recommend you read through the list to ensure you don't rely on a state that might change in the future.
In general, the non-breaking changes include adding functionality or changes in order of the returned data. More specifically, the following are NOT breaking changes:
The API returns standard HTTP status codes to indicate the success or failure of a request. In general, status codes in the
2xx range indicate a successful request, status codes in the
4xx range indicate errors caused by an incorrect input (for example, providing incorrect API key), and status codes in the
5xx range indicate an error on our side.
|The request was not understood. Check your request for a missing required parameter or an invalid query parameter value.|
|The provided API key is invalid or missing.|
|The provided API key is invalid for the requested project.|
|The requested resource doesn't exist. Try checking the resource name for typos.|
|The requested HTTP method is not supported for the specified resource.|
The rate limit for the API has been exceeded. Try your request again after a few seconds as specified in the
|Something went wrong on our side. Try your request again after a few seconds and use a retry policy.|
For troubleshooting failed requests, the API provides error messages defined in a consumable format to help you identify and fix the issue.
The error message explaining what caused the error.
The performed request's unique ID.
integer <int32> [ 1 .. 500 ]
The specific internal code for the type of error. Only useful for finding patterns among error requests.