The collective power of members’ metadata is available for use in a variety of tools and APIs that allow anybody to search and reuse our metadata in sophisticated ways.
Watch the introductory animation in your language:
Lots of people need to incorporate scholarly metadata into their software and services. For example:
The resulting dissemination of metadata enhances content discoverability. The widespread use of our APIs helps to ensure that the entire community can create robust, persistent and accurate citations of our members’ content, to the benefit of publishers, readers and the organizations that use our metadata delivery services.
There are two main approaches for getting metadata:
User interfaces for people: the first table lists a few user interfaces that we provide to access metadata, but you may want to start with our newest, open, most comprehensive, and easiest-to-use human interface, Metadata Search.
APIs for machines: the second table lists a few APIs, but we recommend you first look at our newest and most flexible one, our REST API. Take a look at a list of some of the organizations who rely on our REST API.
If you’re interested in using these tools or APIs for production services, we offer the Metadata Plus service with outputs in either/or JSON or XML, and with extra service and support guarantees. If you are interested in the Plus service please contact our outreach team.
The APIs listed here provide metadata in a variety of representations (aka output formats). If you want to get access to our metadata in a particular representation (e.g. RDF, BibTex, XML, CSL), you can use content negotiation to retrieve the metadata for a DOI in the representation you want. Content negotiation is supported by a number of DOI registration agencies including Crossref, DataCite, and mEDRA.
We have a number of APIs for accessing metadata. There is one general purpose API and several specialized ones. The specialized APIs are either designed for our members so that they can manage their metadata or they are APIs based on standards that are popular in the community.
|REST API||The REST API enables sophisticated, flexible machine and programmatic access to search and filter our metadata. It can be used for example to look up the metadata for a content item or submit a query on an author’s name or find retractions registered with us. It also allows users to search and filter on a number of elements, including a funder, or all content items with ORCID iDs. The REST API is open to all and it’s also included in the Plus service|
|OAI-PMH||This API uses a standard popular with the library community that lets you harvest metadata. This API is included in the Plus service.|
|OpenURL||This API lets you look up a Crossref DOI for a reference using a standard that is popular in the library community and particularly with link resolver services.|
Crossref provides a number of user interfaces to access Crossref metadata. Some are general purpose, and others are more specialized.
|Metadata Search||Metadata Search is our primary user interface for searching and filtering of our metadata. It allows users to quickly enter any term and users can search and filter on a number of elements, including ISSN, ORCIDs, funding data and more.It can be used to lookup the DOI for a reference or a partial reference or a set of references.|
|Simple text query||Simple text query is a tool designed to allow members to easily link their references via DOIs. It allows a member to look up DOIs for multiple formatted references at a time and then deposit these in order to fulfill their reference linking obligations.|
Watch the introductory animation in your language:
It is important that members understand how metadata is used by other software and services in the Crossref community. We encourage members to submit as much metadata as possible so that these tools and services can include your content to their users. If using the Public REST API, please consider including your email address in header requests as we are able to prioritize these “Polite” pool of queries. If you’d like to share a case study for how you use Crossref metadata and be features on our blog, please get in touch.
Our fees page lists costs and descriptions for the Plus service.
We offer help documentation for all metadata delivery services. And documentation about the REST API is available on [Github].
105404354 unique scholarly works are distributed into systems across the research enterprise 24/7 via our metadata APIs, at a rate of around 607 million queries a month. This is a collection of brief user stories from some of the people who rely on Crossref metadata. We use Crossref metadata to… Add funding info from publications to researchers’ portfolios, and report the publications as arising from the grant; to validate the data provided by universities; and we use the license and embargo period information to help understand the open access status of publications.
Give and get metadata that’s open and useful Our REST API exposes the metadata that members provide Crossref when they register their content with us. And it’s not just the bibliographic metadata either. Funding data, license information, full-text links, ORCID iDs, abstracts, and Crossmark updates, are all available, if included in members’ metadata. Numerous tools and services rely on our metadata, be they for search, annotation, sharing, or analysis. Some common tasks for using our REST API include:
Metadata APIs Plus Service The Metadata Plus service provides machine access to all our metadata records in both XML and JSON, with enhanced service and features. For the first time, users may access multiple interfaces under one agreement, providing flexibility, robust functionality and improved support for the diverse and growing needs of the variety of organizations that use metadata in systems and services throughout scholarly communications. Enhancements include: ‘Snapshot’ full-file downloads Guaranteed uptime Priority support We are very excited to share our newest metadata service, called Plus, introduced in 2018.