--- title: Daytona API Reference description: A reference of supported operations using the Daytona API. --- This reference covers the two REST APIs that the Daytona SDKs call. The Daytona API manages platform resources: sandboxes, images, snapshots, volumes, secrets, registries, organizations, projects, and API keys. The Toolbox API runs inside each sandbox and exposes its environment: processes, sessions, files, Git, language servers, and computer use. Both APIs return errors as JSON with an error code, a message, and the error source. This reference is generated from the OpenAPI specification of each API. | **Concept** | **Description** | | ------------------------- | --------------------------------------------------------------------------------------------------- | | **Daytona API** | The API for managing sandboxes and other platform resources. | | **Toolbox API** | The API served inside a running sandbox for processes, files, Git, language servers, and more. | | **Project API key** | The credential for workload operations, scoped to one project and limited to the permissions set at creation. | | **Proxy** | The regional service that authenticates Toolbox API requests and routes them to the sandbox. | | **Sandbox daemon** | The agent inside each sandbox that serves the Toolbox API. | | **OpenAPI specification** | The machine-readable definition of each API, available for download below. | ## OpenAPI specifications Each API has an OpenAPI 3.1 specification in JSON format. A specification lists every operation with its path, parameters, request and response schemas, and error responses. The Daytona API specification also names the permission that each operation requires. Use a specification to generate a client in your language or to import the API into an HTTP client. - Daytona API: [OpenAPI specification](/docs/v2/openapi.json) - Toolbox API: [OpenAPI specification](/docs/v2/toolbox-openapi.json)