GET /geocode/v1/* → endpoint removal
OpenCage Geocoding API
Deprecated, no date
The provider deprecated the query parameter jsonp on GET /geocode/v1/* without a shutdown date, announcing on May 11, 2026, that it is no longer supported. Unsupported calls using this parameter fail, although the provider stated it will continue working for existing customers.
Calls it hits
GET /geocode/v1/*query parameter jsonp
What to use instead of these calls
Drop jsonp and call GET /geocode/v1/json from the browser with CORS using fetch instead.
In OpenCage Geocoding API's words
We no longer support the optional `jsonp` parameter, though it will continue working for existing customers.
Facts
- API
- OpenCage Geocoding API
api.opencagedata.com - Kind
- Endpoint removal
- Announced
- May 11, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against OpenCage Geocoding API's own pages
Questions
When does this change take effect?
OpenCage Geocoding API deprecated GET /geocode/v1/*, query parameter jsonp without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: OpenCage Geocoding API has not given a shutdown date yet.
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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.