Deprecating Retraction Watch annotations in the Labs API

Metadata Retrieval
,
1

Around two and a half years ago, Crossref acquired the Retraction Watch database. To provide immediate access while we developed a permanent production schema, we added this data as annotations in the experimental Labs API.

With the launch of the production schema in January 2025 (see the blog post), the Labs API integration is no longer necessary. To ensure the long-term stability and reliability of our services, we are now deprecating these integrations in the Labs API.

What this means for you

Existing retraction annotations will remain in the Labs API, but no new updates (from either Crossmark or Retraction Watch) will be pushed to that endpoint starting now.

  • If you use the Labs API to fetch the Retraction Watch CSV: This will continue to work for the time being, but we still recommend that you transition to downloading the file directly from GitLab.
  • To check if a DOI has been retracted: Please use the production API. For example, a query for https://api.crossref.org/works/10.1021/am300292v shows this is a retracted document through the following updated-by field:
     "updated-by": [
  {
    "DOI": "10.1021/acsami.9b11759",
    "type": "retraction",
    "label": "Retraction",
    "source": "retraction-watch",
    "updated": {
      "date-parts": [[2019, 7, 26]],
      "date-time": "2019-07-26T00:00:00Z",
      "timestamp": 1564099200000
    },
    "record-id": "20946"
  }
]
    In this example, the retraction was asserted by Retraction Watch in July 2019. The record-id field corresponds to the Retraction Watch database ID, allowing for quick cross-referencing within the Retraction Watch CSV file in case more information is needed.

Using the production REST API ensures you receive the most up-to-date data. Additionally, by using the polite pool, you will benefit from significantly faster response times and improved stability over the Labs API.

In the coming days, we will also reach out directly to users who have provided email addresses in their Labs API queries to notify them of this change.

If you have any technical questions regarding the transition to the production API, please feel free to post a question in this thread.

Thank you for your cooperation as we work to improve the stability of our data services.

4 Likes