We just rolled version 0.5.4 of our JS client!

The big change is that the methods the client makes available are generated at runtime based on the JSON Schema of our CMA. This means any new API endpoint — or changes to existing ones — will instantly be reflected to the client, without the need to upgrade to the latest client version.

We also added a new deserializeResponse option to every call, that you can use if you want to retrieve the exact payload the DatoCMS returns:

1
import { SiteClient } from 'datocms-client';
2

3
const client = new SiteClient("YOUR-API-KEY")
4

5
// `deserializeResponse` is true by default:
6
const accessToken = client.accessTokens.create({
7
  name: "New token",
8
  role: "34"
9
})
10

11
// {
12
//   id: "312",
13
//   hardcodedType: null,
14
//   name: "New token",
15
//   token: "XXXX",
16
//   role: "34"
17
// }
18

19
// if `deserializeResponse` is false, this will be the result
20
const accessToken = client.accessTokens.create(
21
  {
22
    name: "New token",
23
    role: "34"
24
  },
25
  {
26
    deserializeResponse: false
27
  }
28
)
29

30
// {
31
//   data: {
32
//     type: "access_token",
33
//     id: "312",
34
//     attributes: {
35
//       name: "New token",
36
//       token: "XXXX",
37
//       hardcoded_type: nil
38
//     },
39
//     relationships: {
40
//       role: {
41
//         data: {
42
//           type: "role",
43
//           id: "34"
44
//         }
45
//       }
46
//     }
47
//   }
48
// }

In our doc pages we also added some examples for the super-handy allPages option which was already present since v0.3.29:

// if you want to fetch all the pages with just one call:
client.items.all({ "filter[type]" => "44" }, { allPages: true })

We just added support for the new Gatsby v2 fixed and fluid responsive image queries.

Old names (sizes and resolutions) are deprecated but still work.

You can now decide to completely delete your DatoCMS account from the "My account" section of the dashboard.

(Updated Dec 2024)

By default, DatoCMS uses the shared domain www.datocms-assets.com to serve your project's asset files (such as images and PDFs). On Enterprise plans, you can choose to use your own cloud storage and domain name instead.

To get started, please follow the instructions in one of these plugins, and then reach out to support@datocms.com to complete the setup:

DatoCMS External Asset Storage & Custom Domain Options

On an Enterprise plan, you can host your DatoCMS assets (files) on third-party cloud providers with your own domain name. The following providers are supported:

• AWS S3 for DatoCMS assets

• Azure Blob Storage for DatoCMS assets

• Google Cloud Storage for DatoCMS assets

• Cloudflare R2 Storage for DatoCMS assets

We just enabled query batching support to our GraphQL Content Delivery API.

This means you can combine multiple GraphQL operations into a single HTTP request, reducing HTTP overheads. If you use Apollo Client, you can enable batch queries with the apollo-link-batch-http package:

1
import { ApolloClient } from 'apollo-client';
2
import { setContext } from 'apollo-link-context';
3
import { InMemoryCache } from 'apollo-cache-inmemory';
4
import { BatchHttpLink } from 'apollo-link-batch-http';
5

6
const httpLink = new BatchHttpLink({
7
  uri: 'https://graphql.datocms.com/',
8
});
9

10
const authLink = setContext((_, { headers }) => {
11
  return {
12
    headers: {
13
      ...headers,
14
      'Authorization': `Bearer ${process.env.DATO_API_TOKEN}`,
15
    }
16
  }
17
});
18

19
const client = new ApolloClient({
20
  link: authLink.concat(httpLink),
21
  cache: new InMemoryCache(),
22
});
23

24
export default client;

We just rolled version 0.6 of our Ruby client!

The big change is that the methods the client makes available are generated at runtime based on the JSON Schema of our CMA. This means any new API endpoint — or changes to existing ones — will instantly be reflected to the client, without the need to upgrade to the latest client version.

We also added a new deserialize_response option to every call, that you can use if you want to retrieve the exact payload the DatoCMS returns:

1
require "dato"
2
client = Dato::Site::Client.new("YOUR-API-KEY")
3

4
# `deserialize_response` is true by default:
5
access_token = client.access_tokens.create(name: "New token", role: "34")
6

7
# {
8
#   "id" => "312",
9
#   "hardcoded_type" => nil,
10
#   "name" => "New token",
11
#   "token" => "XXXX",
12
#   "role" => "34"
13
# }
14

15
# if `deserialize_response` is false, this will be the result
16
access_token = client.access_tokens.create(
17
  { name: "New token", role: "34" },
18
  deserialize_response: false
19
)
20

21
# {
22
#   "data": {
23
#     "type": "access_token",
24
#     "id": "312",
25
#     "attributes": {
26
#       "name": "New token",
27
#       "token": "XXXX",
28
#       "hardcoded_type": nil
29
#     },
30
#     "relationships": {
31
#       "role": {
32
#         "data": {
33
#           "type": "role",
34
#           "id": "34"
35
#         }
36
#       }
37
#     }
38
#   }
39
# }

In our doc pages we also added some examples for the super-handy all_pages option which was already present since v0.3.29:

# if you want to fetch all the pages with just one call:
client.items.all({ "filter[type]" => "44" }, all_pages: true)

We just published some changes to the way DatoCMS manages project transfers between two accounts.

When you transfer a site, the destination account will receive a request that will have to be manually accepted or declined. If the site is on a paying plan, the destination account will have to specify which billing profile will be used from now on to generate invoices.

We just published the ability to combine AND and OR logical expressions in our GraphQL API! You can read more in our Doc page.

In the same page the different filters available for each type of field are now properly documented.

We just updated our docs to better explain what tree-like collections are and how to use them:

• Introduction

• Content Management API endpoints

• GraphQL Content Delivery API

To make it easier to stay up-to-date with the latest development in DatoCMS, we just made available two Atom RSS feeds:

• Product Changelog RSS feed

• Blog RSS feed