Ability to restrict access to GraphQL/REST endpoints

Why DatoCMS

Happy team

For developers

For digital marketers

For content creators

Enterprise

DatoCMS for Enterprise

Features

Worldwide CDN

Performant, secure, and close to every customer

GraphQL Content API

Develop faster with powerful developer tools

Images API

Endless transformations at your disposal

Video API

Produce videos and serve them fast to any device

Multi-language

Reach global audience with localized content

Dynamic layouts

Easily build dynamic layouts for landing pages

Learn

Documentation

Guides, tutorials and API reference

Blog

Culture, learnings, and announcements

Product updates

Changelog for new features and improvements

Community forum

Ask questions and discuss with your peers

Slack channel

Chat live with other devs in our Slack channel

Support

Got questions? Get in touch with our team

Marketplace

Starter projects

Start with a fully configured DatoCMS project

Community plugins

Easily expand the capabilities of DatoCMS

Hosting & Builds

No matter the stack you're using, we've got you covered

Enterprise apps

Keep your company data secure

Pricing

Contact sales Log in Try for free!

Product Updates

DatoCMS changelog for new features and general improvements

January 29th, 2019

Ability to restrict access to GraphQL/REST endpoints

Content Delivery APIContent Management API

We just made possible to specify which API endpoints an API token can access:

This will prevent from using your ie. production API token to read temporary/draft content using the GraphQL preview endpoint.