E2B API
POST /sandboxes/{id}/connect endpoint removal
Deprecated, no dateSubscribe to E2B APIShare
E2B API deprecated the POST /sandboxes/{id}/connect endpoint without a shutdown date. Calls made to this route are slated for removal and will eventually fail. The operation resumes paused sandboxes and extends TTL while returning sandbox details.
Calls it hits
POST /sandboxes/{id}/connect
What to use instead of these calls
Connect with POST /v2/sandboxes/{sandboxID}/connect instead.
In E2B API's words
Returns sandbox details. If the sandbox is paused, it will be resumed. TTL is only extended. Use POST /v2/sandboxes/{sandboxID}/connect 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/{id}/connect 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 /sandboxesEndpoint 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.