Lusha releases a Tables API synced with its Workspace interface
Lusha's API v2.5.0, released July 21, 2026, adds 24 endpoints for creating and managing persistent contact and company tables that sync two ways with the Lusha Workspace interface.
On July 21, 2026, Lusha published v2.5.0 with Contacts Tables and Companies Tables APIs. Tables created through the API appear immediately in the Lusha Workspace and vice versa, and each response includes a deep link. Existing Prospecting, Enrich, Signals and Lookalike endpoints can write results into a table when a tableId is passed, returning a tableWrite summary. Running a column is asynchronous. On July 27 Lusha pulled back the add-column endpoint pending further work, and in v2.14.0 on September 10 it added a column catalog and a working add-columns endpoint.
The details
- Limits: 500 entity IDs per add or remove call, 50,000 entities per table and 500 tables per account.
- Creating, listing, updating and deleting tables is free; adding companies and reading rows are charged.
- Running a column is charged per row according to the column's credit tier.
- Every table call requires an owner email that resolves to a user on the account.
- The Tables API is labeled beta on Lusha's changelog.
Context
Tables arrived alongside Lusha's July 27, 2026 waterfall enrichment release, which ForgeX Research has covered. The column catalog followed in September, and the October releases covering ICP Fit Score, intent topics and Recommendations sit on the same API version line. Earlier 2026 additions included Webhooks, Website Visitors and Decision Makers APIs.
Not disclosed
- Credit rates for each column tier
- A timeline for the Tables API to leave beta
- Which CRM systems CRM-type columns support
- Vendor
Lusha- Category
- Data & Enrichment
- Announcement type
- Product release
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.




