Daytona API
/api/workspace/* endpoint removal
Stopped workingSubscribe to Daytona APIShare
On May 24, 2026, Daytona removed all /api/workspace/* endpoints entirely. Calls made to /api/workspace/* routes after this date fail. Integrations attempting to use these endpoints must move to the updated routes.
Calls it hits
/api/workspace/*
What to use instead of these calls
Migrate integrations by calling the corresponding /api/sandbox endpoints instead, such as GET /api/sandbox, POST /api/sandbox, and /api/sandbox/{sandboxIdOrName}/….
In Daytona API's words
Additionally, all /api/workspace endpoints are being removed entirely. If you still have integrations hitting /api/workspace routes, migrate them to the corresponding /api/sandbox endpoints.
Facts
- API
- Daytona API
app.daytona.io - Kind
- Endpoint removal
- Announced
- May 24, 2026
- Takes effect
- May 24, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Daytona API's own pages
Questions
When does this change take effect?
Calls to /api/workspace/* on Daytona API stopped working on May 24, 2026.
What happens to calls after May 24, 2026?
They have failed since May 24, 2026.
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
-
No date
GET /api/sandbox/paginatedEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.