@datocms/cda-client
Advanced tools
JS client for DatoCMS GraphQL Content Delivery API based on the browser Fetch API
👉 Visit the DatoCMS homepage or see What is DatoCMS?
A lightweight, TypeScript-ready package that offers various helpers around the native Fetch API to perform GraphQL requests towards DatoCMS Content Delivery API.
This package is built with TypeScript and provides type definitions out of the box. It supports TypedDocumentNode for improved type inference when using gql.tada, GraphQL Code Generator or similar tools.
import { executeQuery } from "@datocms/cda-client";
const query = `
query {
allArticles {
id
title
}
}
`;
const result = await executeQuery(query, {
token: "your-api-token-here",
});
console.log(result);
import { executeQuery } from "@datocms/cda-client";
import { AllArticlesQuery } from "./generated/graphql";
const result = await executeQuery(AllArticlesQuery, {
token: "your-api-token-here",
variables: {
limit: 10,
},
});
console.log(result.allArticles);
npm install @datocms/cda-client
This package provides several utility functions to help you interact with the DatoCMS Content Delivery API using GraphQL.
executeQueryThe main function to execute a GraphQL query against the DatoCMS Content Delivery API.
import { executeQuery } from "@datocms/cda-client";
const result = await executeQuery(query, options);
query: A GraphQL query string, DocumentNode, or TypedDocumentNode.options: An object containing execution options.| Option | Type | Description |
|---|---|---|
token | string | DatoCMS API token (required) Read more |
includeDrafts | boolean | If true, return draft versions of records Read more |
excludeInvalid | boolean | If true, filter out invalid records Read more |
environment | string | Name of the DatoCMS environment for the query Read more |
contentLink | 'vercel-v1' | If true, embed metadata for Content Link Read more |
baseEditingUrl | string | Base URL of your DatoCMS project Read more |
returnCacheTags | boolean | If true, receive Cache Tags associated with the query Read more |
variables | object | Variables to be sent with the query |
fetchFn | function | Custom fetch function (optional) |
requestInitOptions | Partial<RequestInit> | Additional request initialization options (optional) |
autoRetry | boolean | Automatically retry on rate limit (default: true) |
rawExecuteQuerySimilar to executeQuery, but returns both the query result and the full response object. This can be handy when used together with returnCacheTags to actually retrieve the cache tags.
import { rawExecuteQuery } from "@datocms/cda-client";
const [result, response] = await rawExecuteQuery(query, {
token: "your-api-token-here",
returnCacheTags: true,
});
const cacheTags = response.headers.get("x-cache-tags");
executeQueryWithAutoPaginationThis function comes handy when the query contains a paginated collection: behind the scene,
executeQueryWithAutoPagination reworks the passed query and collects the results, so that
it's possible to get a collection of records that is longer than Content Delivery API's result limit.
That is done with a single API call, in a transparent way.
import { executeQueryWithAutoPagination } from "@datocms/cda-client";
const result = await executeQueryWithAutoPagination(query, options);
Parameters are the same available for executeQuery:
query: A GraphQL query string, DocumentNode, or TypedDocumentNode.options: An object containing execution options with the same shape of options for executeQuery.Suppose you want to execute the following query:
query BuildSitemapUrls {
allBlogPosts {
slug
}
entries: allSuccessStories(first: 500) {
...SuccessStoryUrlFragment
}
}
fragment SuccessStoryUrlFragment on SuccessStoryRecord {
slug
}
Well, that's a roadblock: DatoCMS CDA has limitations on the pagination page length (currently 500 items).
That means you should introduce a variable and execute the query multiple times, each time skipping the record that have been returned by the previous query.
executeQueryWithAutoPagination does that on your behalf: the above query is analyzed and rewritten on the fly like this:
query BuildSitemapUrls {
allBlogPosts {
slug
}
splitted_0_entries: allSuccessStories(first: 500, skip: 0) {
...SuccessStoryUrlFragment
}
splitted_500_entries: allSuccessStories(first: 500, skip: 500) {
...SuccessStoryUrlFragment
}
splitted_1000_entries: allSuccessStories(first: 500, skip: 1000) {
...SuccessStoryUrlFragment
}
splitted_1500_entries: allSuccessStories(first: 500, skip: 1500) {
...SuccessStoryUrlFragment
}
splitted_2000_entries: allSuccessStories(first: 500, skip: 2000) {
...SuccessStoryUrlFragment
}
}
fragment SuccessStoryUrlFragment on SuccessStoryRecord {
slug
}
Once executed, the results get collected and recomposed as if nothing happened.
executeQueryWithAutoPagination works only when the query contains only one selection that has
an oversized first: argument (i.e. first: argument surpasses the Content Delivery API's result limit).
If two or more fields have oversiaed patination, the function triggers an error.
The rewritten query must still respect the complexity cost.
rawExecuteQueryWithAutoPaginationAs for executeQuery, also executeQueryWithAutoPagination has a pair raw version that returns both the query result and the full response object.
This can be handy when used together with returnCacheTags to actually retrieve the cache tags.
import { rawExecuteQueryWithAutoPagination } from "@datocms/cda-client";
const [result, response] = await rawExecuteQueryWithAutoPagination(query, {
token: "your-api-token-here",
returnCacheTags: true,
});
const cacheTags = response.headers.get("x-cache-tags");
buildRequestHeadersBuilds request headers for a GraphQL query towards the DatoCMS Content Delivery API.
import { buildRequestHeaders } from "@datocms/cda-client";
const headers = buildRequestHeaders(options);
The buildRequestHeaders function accepts the same options as executeQuery, except for variables, fetchFn, and autoRetry.
buildRequestInitBuilds the request initialization object for a GraphQL query towards the DatoCMS Content Delivery API.
import { buildRequestInit } from "@datocms/cda-client";
const requestInit = buildRequestInit(query, options);
query: A GraphQL query string or DocumentNode.options: An object containing execution options (same as executeQuery).In case a query fails (either with an HTTP status code outside of the 2xx range, or for an error in the query), an ApiError exception will be thrown by the client. This error contains all the details of the request and response, allowing you to debug and handle errors effectively.
import { executeQuery, ApiError } from "@datocms/cda-client";
const query = `
query {
allArticles {
id
title
}
}
`;
try {
const result = await executeQuery(query, {
token: "your-api-token-here",
});
console.log(result);
} catch (e) {
if (e instanceof ApiError) {
// Information about the failed request
console.log(e.query);
console.log(e.options);
// Information about the response
console.log(e.response.status);
console.log(e.response.statusText);
console.log(e.response.headers);
console.log(e.response.body);
} else {
// Handle other types of errors
throw e;
}
}
Contributions are welcome! Please feel free to submit a Pull Request.
This project is licensed under the MIT License.
DatoCMS is the REST & GraphQL Headless CMS for the modern web.
Trusted by over 25,000 enterprise businesses, agencies, and individuals across the world, DatoCMS users create online content at scale from a central hub and distribute it via API. We ❤️ our developers, content editors and marketers!
Why DatoCMS?
Getting Started:
Official Libraries:
Official Framework Integrations
Helpers to manage SEO, images, video and Structured Text coming from your DatoCMS projects:
Additional Resources:
FAQs
JS client for DatoCMS GraphQL Content Delivery API based on the browser Fetch API
We found that @datocms/cda-client demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 6 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now scans OpenVSX extensions, giving teams early detection of risky behaviors, hidden capabilities, and supply chain threats in developer tools.
Product
Bringing supply chain security to the next generation of JavaScript package managers
Product
A safer, faster way to eliminate vulnerabilities without updating dependencies