DataCite REST API
GET /members* endpoint removal
Stopped workingSubscribe to DataCite REST APIShare
On July 1, 2026, DataCite REST API removed the GET /members* endpoints. Following this change, calls to these legacy Version 1 endpoints fail. DataCite REST API retired them due to low usage and in favor of the functionality offered by Version 2.
Calls it hits
GET /members*
What to use instead of these calls
Use the Version 2 endpoint /providers instead, changing requests from /members/{id} to /providers/{id}. Moving to this replacement takes more than an endpoint swap because its 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.
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 /members* 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
-
GET /data-centers*Endpoint removal Stopped working -
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.