Lusha API
POST /v3/{id}/tables/{id}/columns endpoint removal
Stopped workingSubscribe to Lusha APIShare
On July 27, 2026, the POST /v3/{contacts|companies}/tables/{table_id}/columns endpoint stopped working. Documented as shipped in 2.5.0, the action was not yet functional and has been pulled back from both Contacts Tables and Companies Tables. Calls to POST /v3/{id}/tables/{id}/columns fail since July 27, 2026.
Calls it hits
POST /v3/{id}/tables/{id}/columns
What to use instead of these calls
Columns can still be listed, run, and removed, but adding a new column via API is unavailable for now.
In Lusha API's words
Tables: Add Column endpoint pulled back - POST /v3/{contacts|companies}/tables/{table_id}/columns - documented as shipped in 2.5.0, but the action is not yet functional and has been removed from both Contacts Tables and Companies Tables pending further work.
Facts
Questions
When does this change take effect?
Calls to POST /v3/{id}/tables/{id}/columns on Lusha API stopped working on July 27, 2026.
What happens to calls after July 27, 2026?
They have failed since July 27, 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/contacts/decision-makersEndpoint 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.