Okapi Okapi

DataCite REST API GET /data-centers* endpoint removal

Stopped workingSubscribe to DataCite REST APIShare

On July 1, 2026, Version 1 endpoints including GET /data-centers* were removed from the DataCite REST API due to low usage. Requests to these endpoints fail since that date. The change took effect on July 1, 2026.


Calls it hits

  • GET /data-centers*

What to use instead of these calls

Use the Version 2 endpoint /clients instead, changing /data-centers/{id} to /clients/{id}. Note that the response structure differs.

In DataCite REST API's words

Due to the low usage of Version 1 and the improved functionality of the widely-adopted Version 2 successor, Version 1 endpoints will be deprecated on 1 July 2026.

DataCite REST API, Announcement

Facts

API
DataCite REST API api.datacite.org
Kind
Endpoint removal
Takes effect
July 1, 2026
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against DataCite REST API's own pages

Questions

When does this change take effect?

Calls to GET /data-centers* on DataCite REST API stopped working on July 1, 2026.

What happens to calls after July 1, 2026?

They have failed since July 1, 2026.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


More from DataCite REST API 2

  1. GET /members*Endpoint removal Stopped working
  2. GET /works*Endpoint removal Stopped working

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub

Get notifications

Subscribe to DataCite REST API

Hear about each breaking change DataCite REST API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • DataCite REST API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.