Proxycurl API removal
Stopped workingSubscribe to Proxycurl APIShare
On July 4, 2025, Proxycurl API shut down the service and stopped handling requests. This change hits all calls to /proxycurl/api/* endpoints. Any requests sent to these routes after that day fail.
Calls it hits
/proxycurl/api/*
What to use instead of these calls
Remove the Proxycurl calls. Existing keys work with the NinjaPear API at nubela.co/api/v1/..., but it does not serve LinkedIn profile data, requiring a product decision to drop the feature or use another provider.
No replacement for the LinkedIn data Proxycurl served: another data provider or dropping the feature is a product decision.
In Proxycurl API's words
Today, we are shutting Proxycurl down.
Facts
- API
- Proxycurl API
nubela.co - Kind
- Removal
- Announced
- July 4, 2025
- Takes effect
- July 4, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Proxycurl API's own pages
Questions
When does this change take effect?
Calls to /proxycurl/api/* stopped working on July 4, 2025.
What happens to calls after July 4, 2025?
They have failed since July 4, 2025.
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.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.