Access DataCite content negotiation here: https://data.datacite.org

The DataCite content negotiation allows you to retrieve DOI metadata in different formats. A content negotiated request to a DOI resolver is very similar to a standard HTTP request, but based on the list of acceptable content types.

It can be used by an HTTP client by configuring its HTTP Accept headers, or directly through a browser, constructing a URL.

DataCite content negotiation is open to the whole community and does not require authentication. It is particularly designed to provide direct access to all our DOIs, simplify integrations and avoid format conversions.

The DOI proxy at doi.org will normally redirect a user to the resource location URL of a DOI. For example, the DOI "10.5284/1015681" redirects to a landing page describing the dataset, "Excavation of a Romano-British Cemetery...". Content negotiated requests to doi.org that ask for a content type which isn't "text/html" will be redirected to the DataCite content negotiation service.

Normal browser requests or explicit requests for text/html redirect to the content's landing page.

Requests for a data type redirect to a registration agency's metadata service.

Making a content negotiated request requires the use of the Accept HTTP header. Content types that are acceptable to the client (those that it knows how to parse), each with an optional "quality" value indicating its relative suitability. For example, a client that wishes to receive citeproc JSON if it is available, but which can also handle RDF XML if citeproc JSON is unavailable, would make a request with an Accept header listing both "application/citeproc+json" and "application/rdf+xml":

This request favours citeproc JSON but will accept RDF XML if citeproc is unavailable. The q values are optional. The request could have been written without them. The order of content types then becomes important; more suitable content types should be placed at the front of the Accept header.

DataCite supports different response codes, listed below. If multiple content types specified by the client are supported by a DOI then the content type with the highest "q" value (or, if no "q" values are specified, the one that appears first in the "accept" header) will be returned.

DataCite supports link-based content type requests. This method can be used with a regular web browser. In order to get a specific format please construct a URL following this pattern: https://data.datacite.org/MIME_TYPE/DOI.

Extra parameters, e.g. when using the text/x-bliography content type, can be included, e.g.

curl https://data.datacite.org/text/x-bibliography;style=ieee/10.5061/dryad.8515

This method allows DataCite data centres to link additional metadata and data itself using custom URLs, still using the primary URL for the DOI to point to the landing page of a data set.

DataCite supports a number of metadata content types: