Lusha API
POST /v3/contacts/decision-makers endpoint removal
Stopped workingSubscribe to Lusha APIShare
On September 4, 2026, the POST /v3/contacts/decision-makers endpoint was retired and removed from the API reference. Any calls made to this endpoint fail. The change directly affects requests sent to api.lusha.com using POST /v3/contacts/decision-makers.
Calls it hits
POST /v3/contacts/decision-makers
What to use instead of these calls
Call POST /v3/contacts/buying-group, which returns the relevant contacts for a company along with a per-contact relevance score.
In Lusha API's words
POST /v3/contacts/decision-makers has been retired and removed from the API reference. Use [Buying Group](/buying-group/overview), which covers the same use case with a broader persona set and per-contact relevance scoring.
Facts
- API
- Lusha API
api.lusha.com - Kind
- Endpoint removal
- Announced
- September 4, 2026
- Takes effect
- September 4, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Lusha API's own pages
Questions
When does this change take effect?
Calls to POST /v3/contacts/decision-makers on Lusha API stopped working on September 4, 2026.
What happens to calls after September 4, 2026?
They have failed since September 4, 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 Lusha API 1
-
POST /v3/{id}/tables/{id}/columnsEndpoint 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.