Runloop API
POST /v1/devboxes/{id}/execute_sync endpoint removal
Deprecated, no dateSubscribe to Runloop APIShare
The POST /v1/devboxes/{id}/execute_sync endpoint has been deprecated without a shutdown date. Calls made to this endpoint will eventually fail. Runloop API advises that users please use /execute_async instead to synchronously execute a shell command on a Devbox.
Calls it hits
POST /v1/devboxes/{id}/execute_sync
What to use instead of these calls
Start the command with POST /v1/devboxes/{id}/execute_async and read its result from the returned execution.
In Runloop API's words
(Deprecated, please use /execute_async) Synchronously execute a shell command on a Devbox
Facts
- API
- Runloop API
api.runloop.ai - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Runloop API's own pages
Questions
When does this change take effect?
Runloop API deprecated POST /v1/devboxes/{id}/execute_sync without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Runloop 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.