# POST /v3/{contacts|companies}/tables/{table_id}/columns stops working

Calls to POST /v3/{id}/tables/{id}/columns on Lusha API stopped working on July 27, 2026.

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.

## What to use instead

Columns can still be listed, run, and removed, but adding a new column via API is unavailable for now.

- API: Lusha API (api.lusha.com)
- Kind: Endpoint removal
- Announced: July 27, 2026
- Takes effect: July 27, 2026
- Calls after that day: fail
- Calls it hits: `POST /v3/{id}/tables/{id}/columns`
- Source: [Changelog](https://docs.lusha.com/changelog/overview)
- Verified: November 6, 2026, against Lusha API's own pages
- Page: https://www.okapi.bot/providers/lusha-api/breaking-changes/post-v3-contacts-companies-tables-table-id-columns-stops-working/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent
