GET /v5/skill/enrich → endpoint removal
People Data Labs API
Stopped working
On April 15, 2025, the Skill Enrichment API was sunset. Any requests sent to GET /v5/skill/enrich fail because the endpoint is no longer available.
Calls it hits
GET /v5/skill/enrich
What to use instead of these calls
Remove calls to GET /v5/skill/enrich. Because there is no direct replacement, rebuild downstream workflows to search people by skill using the Person Search API (POST /v5/person/search) or enrich titles using the Job Title Enrichment API (GET /v5/job_title/enrich).
No direct replacement: what the skill lookups fed has to be rebuilt on another API.
In People Data Labs API's words
As of the April 2025 (v30.0) release, the Skill Enrichment API has been officially sunset and is no longer available.
Facts
- API
- People Data Labs API
api.peopledatalabs.com - Kind
- Endpoint removal
- Announced
- January 21, 2025
- Takes effect
- April 15, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against People Data Labs API's own pages
Questions
When does this change take effect?
Calls to GET /v5/skill/enrich on People Data Labs API stopped working on April 15, 2025.
What happens to calls after April 15, 2025?
They have failed since April 15, 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.