Next.js + DatoCMS tutorial for beginners
Play video »
Sorry, no results found for "".
Content Delivery API > Content Delivery API Overview
Content Delivery API Overview
This section offers a detailed reference to DatoCMS's Content Delivery API.
The Content Delivery API is used to retrieve content from one of your DatoCMS projects and deliver it to your web or mobile projects.
Our APIs serve content via a powerful and robust content delivery network (CDN). Multiple data centers around the world store a cached copy of your content. When a page request is made, the content is delivered to the user from the nearest server. This greatly accelerates content delivery and reduces latency.
Content Delivery vs Content Management API
If you need to deliver content to your public-facing web or mobile projects, this is the API to use, while if you want to programmatically create or update your schema/content, please refer to the Content Management API!
Why GraphQL?
The Content Delivery API is written in GraphQL, which offers a number of advantages over classic REST APIs:
Strongly typed schema
Many developers have found themselves in situations where they needed to work with deprecated API documentation, lacking proper ways of knowing what operations are supported by an API and how to use them. GraphQL clearly defines the operations supported by the API, including input arguments and possible responses, offering an unfailing contract that specifies the capabilities of an API.
No more over-fetching and under-fetching
Developers often describe the major benefit of GraphQL as the fact that clients can retrieve exactly the data they need from the API. They don’t have to rely on REST endpoints that return predefined and fixed data structures. Instead, the client can dictate the shape of the response objects returned by the API.
Fewer roundtrips
One of the major issues of REST is that, in order to get the data you need, you are forced to call a number of different endpoints. Each API request to pull a resource is a separate HTTP request-response cycle. Fetching complicated data requires multiple round-trips between the client and server to render even a single view. On the contrary, GraphQL enables you to call several related functions without multiple round-trips.
Pro tip: DatoCMS, powered by DatoCMS
Of course, we drink our own champagne - our website is built on DatoCMS.
Want a peek behind the curtain? The actual source code is available in this public GitHub repo for you to explore and see how we built it.
Want to get started with DatoCMS?
If you are new to DatoCMS and you want to learn the basics, check these video tutorials for beginners!
