tl;dr
If you're seeing "Sorry, something went wrong" when using Wikidata reconciliation in OpenRefine, switch your service URL to https://wikidata-reconciliation.wmcloud.org/en/api. A fix is in progress; see details below.
See the video below on how to add a new service
Investigation
It seems @antonin_d set up a redirect from https://wikidata.reconci.link/en/api to https://wikidata-reconciliation.wmcloud.org/en/api
$ curl -sI https://wikidata.reconci.link/en/api
HTTP/1.1 307 Temporary Redirect
Date: Tue, 14 Apr 2026 15:09:01 GMT
Server: Apache/2.4.66 (Debian)
Location: https://wikidata-reconciliation.wmcloud.org/en/api
Content-Type: text/html; charset=iso-8859-1
However, we still have users reporting issues “Add column from reconciled values” fails when typing Wikidata properties manually
So I did a test comparing the feature using both endpoints
With the endpoint hosted on wmcloud
- Reconcile -
working - Search for match - working
- Add a column from reconciled value working
- Add a column from reconciled value > Search Properties working
With the endpoint hosted on wiki-link
- Reconcile, working today, though some users have reported intermittent errors earlier. I suppose the redirect deployed recently fixed the issue.
- Search for match -
error message Sorry, something went wrong. Please try again later
- Add a column from reconciled value - working
- Add a column from reconciled value > Search Properties - error message
Sorry, something went wrong. Please try again later
Technical details
The browser blocks the request at the 307 redirect because the redirect response from wikidata.reconci.link does not carry an Access-Control-Allow-Origin header. Chrome's console shows:
HTTP/1.1 307 Temporary Redirect
Date: Tue, 14 Apr 2026 14:57:43 GMT
Server: Apache/2.4.66 (Debian)
Location: https://wikidata-reconciliation.wmcloud.org/en/suggest/entity?prefix=Newcastle%20University&spell=always&exact=false&prefixed=true
Content-Length: 480
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Status = CORS error
The final wmcloud endpoint does return the CORS header correctly, but the browser rejects the 307 before following the redirect.
