A common API to get all metadata from DataCite.

Version History

  • v.1: June 25, 2016, first draft.
  • v.1.1: October 31, 2016, follow JSONAPI spec for side-loading associations Changelog
  • v.1.2: February 5, 2017, simplified API


The API is generally RESTFUL and returns results in JSON. The API follows the JSONAPI specification.

Results Overview

All results are returned in JSON. There are two general types of results:

  • Singletons
  • Lists

The mime-type for API results is application/vnd.api+json.


Singletons are single results. Retrieving metadata for a specific identifier (e.g. DOI, ORCID) typically returns in a singleton result.


Lists results can contain multiple entries. Searching or filtering typically returns a list result. A list has three parts:

  • meta, which includes information about the query, e.g. number of results returned.
  • data, which will contain the items matching the query or filter.
  • included, which will contain side-loaded associations, via the ?include=x parameter.

Sort order

If the API call includes a query, then the sort order will be by the relevance score. If no query is included, then the sort order will be by DOI deposit date.

Resource Components

Major resource components supported by the DataCite API are (in alphabetical order):

  • data-centers
  • members
  • pages
  • people
  • works

These can be used alone like this

Resource Description
/data-centers returns a list of all DataCite data centers
/members returns a list of all DataCite members
/pages returns a list of posts from the DataCite blog
/people returns a list of all people registered with the Profiles service
/works returns a list of all works (datasets, text documents, etc.), 25 per page

Resource components and identifiers

Resource components can be used in conjunction with identifiers to retrieve the metadata for that identifier.

Resource Description
/data-centers/{data-center-id} returns metadata for a DataCite data center
/members/{member-id} returns metadata for a DataCite member
/people/{orcid} returns metadata for a person registered with DataCite Profiles
/works/{doi} returns metadata for the specified DataCite DOI.


Parameters can be used to query, filter and control the results returned by the DataCite API. They can be passed as normal URI parameters or as JSON in the body of the request.

Parameter Description
query limited DisMax query terms
rows results per per page
offset result offset
sort sort results by a certain field
order set the sort order to asc or desc
include side-load associations (see below)

Example query using URI parameters


Queries support a subset of DisMax, so, for example you can refine queries as follows.

Works that include “renear” but not “ontologies”:


Results from a listy response can be sorted by applying the sort and order parameters. Order sets the result ordering, either asc or desc. Sort sets the field by which results will be sorted. Possible values are:

Sort value Description
score Sort by relevance score
updated Sort by date of most recent change to metadata
deposited Sort by time of most recent deposit
published Sort by publication date

An example that sorts results in order of publication, beginning with the least recent:

Facet Counts

Facet counts are returned via the meta object. Facet counts give counts per field value for an entire result set. The following facet counts are returned:

Resource Facet counts
/data-centers total, members, registration-agencies
/works total, data-centers, relation-types, resource-types, schema-versions, sources, years

All other resources return only total in the meta object.

Filter Names

Filters allow you to narrow queries. All filter results are lists. The following filters are supported:

Filter Possible values Description
member-id {member-id} metadata associated with a specific DataCite member
data-center-id {data-center-id} metadata associated with a specific DataCite data center
resource-id {resource-type-id} metadata for a specific resourceTypeGeneral
relation-type-id {relation-type-id} metadata associated with a specific relation type
from-created-date {date} metadata where deposited date is since (inclusive) {date}
until-created-date {date} metadata where deposited date is before (inclusive) {date}
from-update-date {date} metadata where updated date is since (inclusive) {date}
until-update-date {date} metadata where updated date is before (inclusive) {date}
year {year} publication year of the resource {year}

Notes on owner prefixes

The prefix of a DataCite DOI does NOT indicate who currently owns the DOI.

DataCite also has publisher_id (datacentre_symbol in the DataCite metadata) for depositing organisations. A single publisher may control multiple owner prefixes, which in turn may control a number of DOIs. When looking at works published by a certain organisaton, publisher IDs and the publisher routes should be used.

Notes on dates

Note that dates in filters should always be of the form YYYY-MM-DD, YYYY-MM or YYYY. Also note that the date published in DataCite metadata is always expressed as YYYY (the publicationYear field).


Normally, results are returned 25 at a time. You can control the number of results returns by using the rows parameter. To limit results to 5, for example, you could do the following:

If you would just like to get the summary of the results, you can set the rows to 0 (zero).

The maximum number rows you can ask for in one query is 1000.


The number of returned items is controlled by the rows parameter, but you can select the offset into the result list by using the offset parameter. So, for example, to select the second set of 5 results (i.e. results 6 through 10), you would do the following:


To sideload associations (as specified in the JSONAPI documentation) use the include parameter, for example:,resource-type

Sideload multiple assocations by providing them in a comma-separated list. The following resources can be sideloaded:

Resource Resources that can be included
/data-centers member, registration-agency
/members data-center, registration-agency
/works data-center, member, registration-agency, resource-type, work-type

Example Queries

All works published by data center cdl.dryad (Dryad), with included resource-type

All members with data in their name (e.g. Australian National Data Service), with included data centers

Error messages

When an error occurs, the API will return a JSONAPI error object, for example

  "errors": [
      "status": "422",
      "title":  "Invalid Attribute"