Skip to main content

E2B connector

Back to the connector overview, authentication methods, and actions.
11 Sept 2026
releasePromoted to GA. Version normalized to 1.0.0 in line with the GA versioning policy (GA connectors are versioned 1.0.0 or higher); no functional changes in this version.
11 Sept 2026
description-fixCorrected the pagination and reference documentation on the list actions — the next-page cursor comes back in the response body, not in an X-Next-Token header, and List Sandboxes no longer advertises a total running count that the response never carries, so counting means paging until the cursor is absent. Get Build Logs now states that a 502 from the temporary store is permanent rather than transient and those logs are read from the persistent store, Start Build’s command fields note that a local service is addressed without a URL scheme, and Compose Files points at documentation matching the endpoint it calls.
e2b_compose_files, e2b_get_build_logs, e2b_list_sandboxes, e2b_list_secrets, e2b_list_snapshots, e2b_list_template_builds, e2b_list_templates, e2b_start_build
9 Sept 2026
bug-fix description-fixGet Sandbox Health and Start Build now return an explicit confirmation message instead of an empty string, so a successful call is no longer indistinguishable from no data. Descriptions were corrected across templates and sandboxes — E2B’s public built-in aliases such as “base” are accepted by Create Sandbox and its filters even though List Templates never returns them, Check Template Alias and List Template Builds only accept team-owned aliases and opaque IDs respectively, build logs read from the temporary store only while the builder is alive, and Fork Sandbox and Create Snapshot both require a running sandbox.
e2b_check_template_alias, e2b_create_sandbox, e2b_create_snapshot, e2b_fork_sandbox, e2b_get_build_logs, e2b_get_sandbox_health, e2b_list_sandboxes, e2b_list_template_builds, e2b_list_templates, e2b_start_build
3 Sept 2026
new-connector new-actionsInitial action mappings for the E2B API — 57 actions covering sandbox lifecycle, in-sandbox filesystem and process control, template builds and tags, persistent volumes, secrets, and usage metrics.