E2B API
POST /sandboxes endpoint removal
Deprecated, no dateSubscribe to E2B APIShare
The POST /sandboxes endpoint has been deprecated without a shutdown date, and affected requests will eventually fail. This change impacts calls made directly to create a sandbox from a template. E2B API advises that all system communication is secured under the newer interface.
Calls it hits
POST /sandboxes
What to use instead of these calls
Create sandboxes using POST /v2/sandboxes instead. JavaScript and Python SDKs version 2.51.0 and later call this replacement endpoint automatically.
In E2B API's words
Create a sandbox from the template. All system communication with the sandbox is secured. Use POST /v2/sandboxes instead.
Facts
- API
- E2B API
api.e2b.app - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against E2B API's own pages
Questions
When does this change take effect?
E2B API deprecated POST /sandboxes without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: E2B API has not given a shutdown date yet.
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 E2B API 3
-
No date
GET /sandboxesEndpoint removal Deprecated, no date -
No date
GET /sandboxes/{id}/logsEndpoint removal Deprecated, no date -
No date
POST /sandboxes/{id}/connectEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.