E2B API
GET /sandboxes/{id}/logs endpoint removal
Deprecated, no dateSubscribe to E2B APIShare
E2B API deprecated the GET /sandboxes/{id}/logs endpoint without a shutdown date. This deprecation affects all requests calling GET /sandboxes/{id}/logs to retrieve sandbox logs. Once removed, requests sent to this endpoint fail.
Calls it hits
GET /sandboxes/{id}/logs
What to use instead of these calls
Read logs with GET /v2/sandboxes/{sandboxID}/logs instead.
In E2B API's words
Get sandbox logs. Use /v2/sandboxes/{sandboxID}/logs 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 GET /sandboxes/{id}/logs 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
POST /sandboxesEndpoint 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.