From 25 February 2025, we will be adding redirects for aliased DOIs in the REST API. This means that requests won’t return aliased DOIs.
What is aliasing?
DOIs are persistent identifiers and can’t be deleted, but sometimes they get assigned to the wrong thing. Usually this can be corrected but occasionally it’s necessary to create a new DOI for the same item. Unfortunately that means that there can be two identifiers for the same thing, which can be confusing.
To solve this, we allow members to alias one DOI to another. This means that one DOI (the aliased DOI) is effectively replaced by another DOI (the prime DOI) and a request for the aliased DOI using https://doi.org/DOI resolves to the resolution URL of the prime DOI.
What will happen now?
You will see a few changes in the Crossref REST API after the changes have been implemented:
- If you request the record of an aliased DOI you will get back the prime DOI record instead (with a 301 http status).
- Aliased DOIs won’t appear in the results of queries, only prime DOIs.
- Citation counts and other statistics related to an aliased DOI will be added to the count for the prime DOIs.
- Snapshots in JSON format and the annual data file will only contain prime DOIs.
The XML and OAI-PMH endpoints won’t be affected.
The changes won’t be noticeable in most cases as the number of aliased DOIs is very small, but be aware that you may see a high rate of 301 statuses and some changes in the number of results for certain queries.