# contentful-management.js
JavaScript SDK for Contentful's Content Management API.
Contentful provides a content infrastructure for digital teams to power content in websites, apps, and devices. Unlike a CMS, Contentful was built to integrate with the modern software stack. It offers a central hub for structured content, powerful management and delivery APIs, and a customizable web app that enable developers and content creators to ship digital products faster.
- Content management and retrieval through Contentful's Content Management API.
- Built in rate limiting with recovery procedures
- Asset processing helpers
Browsers and Node.js:
- Chrome
- Firefox
- Edge
- Safari
- node.js (LTS)
- IE11 (with legacy version of the library)
Other browsers should also work, but at the moment we're only running automated tests on the browsers and Node.js versions specified above.
To get started with the Contentful Management JS SDK you'll need to install it, and then get credentials which will allow you to access your content in Contentful.
- Installation
- Authentication
- Using ES6 import
- Your first request
- Troubleshooting
- Documentation/References
Using npm:
npm install contentful-management
Using yarn:
yarn add contentful-management
For browsers, we recommend to download the SDK via npm or yarn to ensure 100% availability.
If you'd like to use a standalone built file you can use the following script tag or download it from jsDelivr, under the dist
directory:
<script src="https://cdn.jsdelivr.net/npm/regenerator-runtime@latest/runtime.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/contentful-management@latest/dist/contentful-management.browser.min.js"></script>
It's not recommended to use the above URL for production.
Using contentful@latest
will always get you the latest version, but you can also specify a specific version number:
<!-- Avoid using the following url for production. You can not rely on its availability. -->
<script src="https://cdn.jsdelivr.net/npm/contentful-management@7.3.0/dist/contentful-management.browser.min.js"></script>
The Contentful Management SDK will be accessible via the contentfulManagement
global variable.
Check the releases page to know which versions are available.
This library also comes with typings to use with typescript.
To get content from Contentful, an app should authenticate with an OAuth bearer token.
If you want to use this SDK for a simple tool or a local app that you won't redistribute or make available to other users, you can get an API key for the Management API at our Authentication page.
If you'd like to create an app which would make use of this SDK but that would be available for other users, where they could authenticate with their own Contentful credentials, make sure to also check out the section about Creating an OAuth Application
You can use the es6 import with the SDK as follow
// import createClient directly
import { createClient } from 'contentful-management'
const client = createClient({
// This is the access token for this space. Normally you get the token in the Contentful web app
accessToken: 'YOUR_ACCESS_TOKEN',
})
//....
OR
// import everything from contentful
import * as contentful from 'contentful-management'
const client = contentful.createClient({
// This is the access token for this space. Normally you get the token in the Contentful web app
accessToken: 'YOUR_ACCESS_TOKEN',
})
// ....
The following code snippet is the most basic one you can use to get content from Contentful with this SDK:
const contentful = require('contentful-management')
const client = contentful.createClient({
// This is the access token for this space. Normally you get the token in the Contentful web app
accessToken: 'YOUR_ACCESS_TOKEN',
})
// This API call will request a space with the specified ID
client.getSpace('spaceId').then((space) => {
// This API call will request an environment with the specified ID
space.getEnvironment('master').then((environment) => {
// Now that we have an environment, we can get entries from that space
environment.getEntries().then((entries) => {
console.log(entries.items)
})
// let's get a content type
environment.getContentType('product').then((contentType) => {
// and now let's update its name
contentType.name = 'New Product'
contentType.update().then((updatedContentType) => {
console.log('Update was successful')
})
})
})
})
You can try and change the above example at Tonic.
Starting contentful-management@7
this library provides an alternative plain SDK which exposes all CMA endpoints in a simple flat manner oppose to a default waterfall structure.
const contentful = require('contentful-management')
const plainClient = contentful.createClient(
{
// This is the access token for this space. Normally you get the token in the Contentful web app
accessToken: 'YOUR_ACCESS_TOKEN',
},
{ type: 'plain' }
)
const environment = await plainClient.environment.get({
spaceId: '<space_id>',
environmentId: '<environment_id>',
})
const entries = await plainClient.entry.getMany({
spaceId: '123',
environmentId: '',
query: {
skip: 10,
limit: 100,
},
})
// With scoped space and environment
const scopedPlainClient = contentful.createClient(
{
// This is the access token for this space. Normally you get the token in the Contentful web app
accessToken: 'YOUR_ACCESS_TOKEN',
},
{
type: 'plain',
defaults: {
spaceId: '<space_id>',
environmentId: '<environment_id>',
},
}
)
// entries from '<space_id>' & '<environment_id>'
const entries = await scopedPlainClient.entry.getMany({
query: {
skip: 10,
limit: 100,
},
})
The benefits of using the plain version of SDK are:
- The ability to reach any possible CMA endpoint without the necessity to call any async functions beforehand.
- It's especially important if you're using this CMA client for non-linear scripts (for example, a complex Front-end application)
- All returned objects are simple Javascript objects without any wrappers. They can be easily serialized without an additional
toPlainObject
function call. - The ability to scope CMA client instance to a specific
spaceId
,environmentId
, andorganizationId
when initializing the client.- You can pass a concrete values to
defaults
and omit specifying these params in actual CMA methods calls.
- You can pass a concrete values to
- I can't Install the package via npm - Check your internet connection - It is called
contentful-management
and notcontenful-management
¯\_(ツ)_/¯ - Can I use the SDK in react native projects - Yes it is possible
- I get the error: Unable to resolve module
http
- Our SDK is supplied as node and browser version. Most non-node environments, like React Native, act like a browser. To force using of the browser version, you can require it via:const { createClient } = require('contentful-management/dist/contentful-management.browser.min.js')
- I am not sure what payload to send when creating and entity (Asset/Entity/ContentType etc...) - Check the Content Management API docs or the examples in the reference docs - Feel free to open an issue if you didn't find what you need in the above links
- 😱 something is wrong what should I do - If it is a bug related to the code create a GitHub issue and make sure to remove any credential for your code before sharing it. - If you need to share your credentials, for example you have an issue with your space, please create a support ticket. - Please do not share your management token in a GitHub issue
To help you get the most out of this SDK, we've prepared reference documentation, tutorials and other examples that will help you learn and understand how to use this library.
The createClient
method supports several options you may set to achieve the expected behavior:
contentful.createClient({
... your config here ...
})
Your CMA access token.
Set the host used to build the request URI's.
Set the host used to build the upload related request uri's.
This path gets appended to the host to allow request urls like https://gateway.example.com/contentful/
for custom gateways/proxies.
Custom agent to perform HTTP requests. Find further information in the axios request config documentation.
Custom agent to perform HTTPS requests. Find further information in the axios request config documentation.
Additional headers to attach to the requests. We add/overwrite the following headers:
- Content-Type:
application/vnd.contentful.management.v1+json
- X-Contentful-User-Agent:
sdk contentful-management.js/1.2.3; platform node.js/1.2.3; os macOS/1.2.3
(Automatically generated)
Axios proxy configuration. See the axios request config documentation for further information about the supported values.
By default, this SDK is retrying requests which resulted in a 500 server error and 429 rate limit response. Set this to false
to disable this behavior.
Errors and warnings will be logged by default to the node or browser console. Pass your own log handler to intercept here and handle errors, warnings and info on your own.
Interceptor called on every request. Takes Axios request config as an arg. Default does nothing. Pass your own function to log any desired data.
Interceptor called on every response. Takes Axios response object as an arg. Default does nothing. Pass your own function to log any desired data.
The Contentful's JS SDK reference documents what objects and methods are exposed by this library, what arguments they expect and what kind of data is returned.
Most methods also have examples which show you how to use them.
You can start by looking at the top level contentfulManagement
namespace.
The ContentfulClientAPI
namespace defines the methods at the Client level which allow you to create and get spaces.
The ContentfulSpaceAPI
namespace defines the methods at the Space level which allow you to create and get entries, assets, content types and other possible entities.
The Entry
, Asset
and ContentType
namespaces show you the instance methods you can use on each of these entities, once you retrieve them from the server.
From version 1.0.0 onwards, you can access documentation for a specific version by visiting
https://contentful.github.io/contentful-management.js/contentful-management/<VERSION>
Read the Contentful for JavaScript page for Tutorials, Demo Apps, and more information on other ways of using JavaScript with Contentful
This library is a wrapper around our Contentful Management REST API. Some more specific details such as search parameters and pagination are better explained on the REST API reference, and you can also get a better understanding of how the requests look under the hood.
For versions prior to 1.0.0, you can access documentation at https://github.com/contentful/contentful-management.js/tree/legacy
This project strictly follows Semantic Versioning by use of semantic-release.
This means that new versions are released automatically as fixes, features or breaking changes are released.
You can check the changelog on the releases page.
The bundle for browsers is now called contentful-management.browser.min.js
to mark it clearly as browser only bundle. If you need to support IE 11 or other old browsers, you may use the contentful-management.legacy.min.js
. Node will automatically use the contentful-management.node.min.js
while bundlers like Webpack will resolve to the new ES-modules version of the library.
No changes to the API of the library were made.
contentful.js 1.x was a major rewrite, with some API changes. While the base functionality remains the same, some method names have changed, as well as some internal behaviors.
See the migration guide for more information.
If you have a problem with this library, please file an issue here on GitHub.
If you have other problems with Contentful not related to this library, you can contact Customer Support.
See CONTRIBUTING.md
MIT