Daytona + Stream Deck

Archives a sandbox in the Daytona platform. Use this action when you need to archive a sandbox that is no longer needed but should be preserved for future reference. The sandbox will be marked as archived and its state will change to reflect the archival status. Note: Archiving a sandbox does not delete it immediately. The sandbox can potentially be restored or recovered from an archived state depending on the platform configuration.

Cancels a pending organization invitation. Use when you need to revoke an invitation that has been sent but not yet accepted by the recipient. This action is irreversible — once an invitation is cancelled, it cannot be reactivated and the recipient will no longer be able to accept it. The cancelled invitation would need to be re-sent as a new invitation if access is still desired.

Checks if the authenticated user has access to a specific sandbox. Use this action when you need to verify whether the current user has permission to access a particular sandbox before performing further operations on it. This is a read-only operation that does not modify any sandbox data.

[DEPRECATED] Checkout a branch or commit in a git repository within a sandbox. Use this action when you need to switch branches or checkout a specific commit in a git repository that exists within a sandbox toolbox. This operation modifies the working tree of the repository. Note: This endpoint is deprecated. Consider using alternative approaches for git operations if available. The sandbox must be in a running state for this operation to succeed.

Clones a Git repository into a sandbox toolbox. Use this action when you need to clone a public or private Git repository into a specific directory within a sandbox. Supports optional branch selection and commit checkout. This is commonly used to set up a development environment or fetch source code for further operations. Note: Credentials (username/password) should only be provided when the target repository requires authentication. The sandbox must be running to perform this operation.

Creates a new API key for the organization. Use when you need to generate a new API key that can be used to authenticate API requests. The created API key value is only returned once in the response and cannot be retrieved again, so it must be stored securely. This action requires appropriate organization permissions.

Creates a new Docker registry for the organization. Use when you need to register a new container registry (such as Docker Hub, GCR, ECR, or other Docker registries) so that Daytona can pull images from it. The registry credentials are stored securely and used for pulling images when creating sandboxes. Ensure the provided credentials have appropriate permissions (typically read access to the registry).

Creates a new folder inside a sandbox's filesystem. Use this action when you need to create a directory within a running sandbox's filesystem. This is useful for organizing files, preparing directory structures, or setting up paths for subsequent file operations. Note: This endpoint is deprecated. Consider using alternative methods for folder creation if available.