/api/v1/w/{}/spaces/{}/apps* → endpoint removal
Dust API
Deprecated, no date
Dust has deprecated the /api/v1/w/{}/spaces/{}/apps* endpoints without announcing a shutdown date. Only Dust Apps created before October 2025 remain accessible, while other requests to these endpoints fail.
Calls it hits
/api/v1/w/{}/spaces/{}/apps*
What to use instead of these calls
Move the app to a Dust agent and call it through the conversations API at POST /api/v1/w/{wId}/assistant/conversations. This transition takes more than changing an endpoint identifier, as Dust Apps have no direct replacement and rebuilding an app as an agent changes how it runs.
Dust Apps have no direct replacement: rebuilding an app as an agent changes how it runs.
In Dust API's words
Dust Apps are deprecated. Only Dust Apps created before October 2025 are accessible.
Facts
- API
- Dust API
dust.tt - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Dust API's own pages
Questions
When does this change take effect?
Dust API deprecated /api/v1/w/{}/spaces/{}/apps* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Dust 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.