Daytona API
GET /api/sandbox/paginated endpoint removal
Deprecated, no dateSubscribe to Daytona APIShare
Daytona API deprecated the GET /api/sandbox/paginated endpoint without a shutdown date. Calls to this endpoint will eventually fail once it is removed. The deprecation follows updates to the standard sandbox listing endpoint to include pagination and search capabilities.
Calls it hits
GET /api/sandbox/paginated
What to use instead of these calls
List sandboxes using GET /api/sandbox instead, which now paginates with a cursor and supports search.
In Daytona API's words
The GET /api/sandbox endpoint now returns a paginated response object with full search capabilities built in, and the legacy /api/sandbox/paginated endpoint is being deprecated.
Facts
- API
- Daytona API
app.daytona.io - Kind
- Endpoint removal
- Announced
- May 24, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Daytona API's own pages
Questions
When does this change take effect?
Daytona API deprecated GET /api/sandbox/paginated without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Daytona 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 Daytona API 1
-
/api/workspace/*Endpoint removal Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.