Changelog

Overview

The Benchling v3 REST API is now generally available. Built on a single shared definition layer, v3 behaves consistently across the whole API, more than doubles endpoint coverage, and adds full write coverage across the Benchling Platform. We recommend that all new integrations build on v3 and that existing v2 integrations begin planning their migration.

Availability

V3 became generally available on October 15, 2026. All stable and beta endpoints are documented in the API Reference. Beta endpoints are marked as such and are accessed by setting the EARLY-ACCESS to true .

Validated Cloud tenants: V3 is part of the 2027.1 release. It can be enabled sooner upon request. Contact your account team to get started.

What’s New

• Core Platform APIs: Create and update schemas, work with structured tables, build custom actions, export audit logs, and filter broadly across list endpoints.
• V3 SDK: A Python SDK generated from the API spec that handles async task polling, multi-step bulk imports, and webhook verification.
• Search API (beta): Search across Benchling with each user’s permissions applied.
• Enterprise and scale: Bulk data movement across all objects, plus management of users, teams, projects, collaborations, and policies.
• Batch create and update: Write up to 25 objects in a single synchronous request on every write endpoint.
• Clear stability guarantees: Stable endpoints get at least 90 days’ notice before breaking changes, except for urgent security and bug fixes that cannot wait for the notice period. Beta endpoints (via the EARLY-ACCESS: true header) may change without notice.

For more on the platform release, see Benchling Platform: The infrastructure behind the next era of science

Next Steps: Migrating from v2 to v3

• v2 deprecation: The deprecation period begins with the 2027.1 ValCloud release.
• Migration guide and tooling are coming soon. We’ll announce them in this changelog. Subscribe via RSS to be notified.

Questions or feedback? Reach out in the Benchling Community or via your account team.