> ## Documentation Index > Fetch the complete documentation index at: https://docs.storiza.store/llms.txt > Use this file to discover all available pages before exploring further. # Run a command in the container > Run a command inside the running container and wait for it to finish. `GET /apps/{id}/terminal` reaches the same place interactively; this is the shape a script or an agent can use — argv in, output and exit code out, no session to hold open. **Exec form.** `["ls", "-la", "/data"]` — each element is one argument and nothing goes through a shell, so `&&`, pipes and globs need a shell asked for by name: `["sh", "-lc", "ls /data | wc -l"]`. This is `docker exec`, not the app's start command: nothing here changes how the container starts, and the process ends when the command does. Bounded on both axes. Output stops at 1 MB and comes back with `truncated: true`; the call is abandoned after `timeoutMs` with `timedOut: true` and `exitCode: null`, which means the command may still be running inside the container. stdout and stderr are interleaved in the order the container produced them. **Required API key permission:** `apps:write` ## OpenAPI ````yaml /openapi.json post /apps/{id}/exec openapi: 3.0.0 info: title: Storiza API version: '1.0' description: Manage Storiza servers, apps and subscriptions programmatically. servers: - url: https://api.storiza.store security: - bearerAuth: [] tags: - name: Servers description: Create, order, renew and upgrade VPS servers, and read their details. - name: Server power & commands description: >- Start, stop, reboot and force-stop a server, check its status and run commands on it. - name: Server settings description: >- Rename a server, reinstall its operating system and follow its installation. - name: Server firewall description: Turn a server's firewall on or off and manage its rules. - name: Server metrics description: CPU, memory, disk and network usage, now and over time. - name: Server backups description: Order the backup add-on, and take, list and delete backups. - name: Server snapshots description: Take, list and delete snapshots of a server. - name: Server sharing description: A share link that lets someone else open the server. - name: Server catalog description: >- Plans, operating systems, categories, datacenters and backup plans. Public — no key needed. - name: Apps description: >- Deploy, order, renew and configure apps — game servers, databases and bots. - name: App lifecycle & console description: >- Start, stop, restart and kill an app, read its output and metrics, and send it commands. - name: App files description: >- Read, write, move and delete the files in an app's volume, and its SFTP access. - name: App backups description: Back up an app, download a backup, and restore from one. - name: App domains description: Your own domains for an app, and their DNS verification. - name: App groups description: Private networks that let your apps reach each other by hostname. - name: App catalog description: Templates, plans and locations for apps. - name: Subscriptions description: What you pay for, how often it renews, and stopping or resuming it. - name: Payments description: >- Follow a payment after an order, and the methods and currencies you can pay with. - name: Account description: Your profile, and a summary of everything you own. - name: SSH keys description: Public keys you can install on new Linux servers. paths: /apps/{id}/exec: post: tags: - App lifecycle & console summary: Run a command in the container description: >- Run a command inside the running container and wait for it to finish. `GET /apps/{id}/terminal` reaches the same place interactively; this is the shape a script or an agent can use — argv in, output and exit code out, no session to hold open. **Exec form.** `["ls", "-la", "/data"]` — each element is one argument and nothing goes through a shell, so `&&`, pipes and globs need a shell asked for by name: `["sh", "-lc", "ls /data | wc -l"]`. This is `docker exec`, not the app's start command: nothing here changes how the container starts, and the process ends when the command does. Bounded on both axes. Output stops at 1 MB and comes back with `truncated: true`; the call is abandoned after `timeoutMs` with `timedOut: true` and `exitCode: null`, which means the command may still be running inside the container. stdout and stderr are interleaved in the order the container produced them. **Required API key permission:** `apps:write` parameters: - schema: type: string format: uuid required: true name: id in: path requestBody: content: application/json: schema: type: object properties: command: type: array items: type: string minLength: 1 maxLength: 4096 minItems: 1 maxItems: 100 timeoutMs: type: integer minimum: 1000 maximum: 120000 workingDir: type: string maxLength: 4096 user: type: string maxLength: 256 required: - command responses: '200': description: Command finished content: application/json: schema: type: object properties: success: type: boolean enum: - true message: type: string enum: - Command finished data: type: object properties: output: type: string exitCode: type: number nullable: true truncated: type: boolean timedOut: type: boolean required: - output - exitCode - truncated - timedOut required: - success - message - data '401': description: Authentication required | Invalid API key | API key has expired content: application/json: schema: type: object properties: success: type: boolean enum: - false type: type: string code: type: string error: type: string details: nullable: true required: - success - type - code - error examples: authenticationRequired: summary: Authentication required value: success: false type: API code: AUTHENTICATION_ERROR error: Authentication required invalidApiKey: summary: Invalid API key value: success: false type: API code: INVALID_API_KEY error: Invalid API key expiredApiKey: summary: API key has expired value: success: false type: API code: EXPIRED_API_KEY error: API key has expired '403': description: >- Account is banned | Account is suspended | Insufficient permissions | This endpoint cannot be accessed with this authentication method | API key lacks the permission required for this endpoint | This API key is not permitted from your IP address content: application/json: schema: type: object properties: success: type: boolean enum: - false type: type: string code: type: string error: type: string details: nullable: true required: - success - type - code - error examples: accountBanned: summary: Account is banned value: success: false type: API code: ACCOUNT_BANNED error: Account is banned accountSuspended: summary: Account is suspended value: success: false type: API code: ACCOUNT_SUSPENDED error: Account is suspended insufficientPermissions: summary: Insufficient permissions value: success: false type: API code: AUTHORIZATION_ERROR error: Insufficient permissions transportNotAllowed: summary: >- This endpoint cannot be accessed with this authentication method value: success: false type: API code: TRANSPORT_NOT_ALLOWED error: >- This endpoint cannot be accessed with this authentication method missingPermission: summary: API key lacks the permission required for this endpoint value: success: false type: API code: MISSING_PERMISSION error: API key lacks the permission required for this endpoint ipNotAllowed: summary: This API key is not permitted from your IP address value: success: false type: API code: IP_NOT_ALLOWED error: This API key is not permitted from your IP address '404': description: App not found content: application/json: schema: type: object properties: success: type: boolean enum: - false type: type: string code: type: string error: type: string details: nullable: true required: - success - type - code - error examples: appNotFound: summary: App not found value: success: false type: API code: APP_NOT_FOUND error: App not found '409': description: The app is stopped — there is no container to run in content: application/json: schema: type: object properties: success: type: boolean enum: - false type: type: string code: type: string error: type: string details: nullable: true required: - success - type - code - error examples: appStopped: summary: The app is stopped — there is no container to run in value: success: false type: API code: APP_STOPPED error: The app is stopped — there is no container to run in '422': description: Validation error content: application/json: schema: type: object properties: success: type: boolean enum: - false type: type: string enum: - API code: type: string enum: - VALIDATION_ERROR error: type: string enum: - Validation error details: type: object additionalProperties: type: object properties: _errors: type: array items: type: string required: - success - type - code - error - details example: success: false type: API code: VALIDATION_ERROR error: Validation error details: _errors: - The whole schema has some validation problems some_field: _errors: - This field has some validation problem '500': description: Internal Server Error content: application/json: schema: type: object properties: success: type: boolean enum: - false type: type: string enum: - API code: type: string enum: - INTERNAL_ERROR error: type: string enum: - Internal server error details: nullable: true required: - success - type - code - error example: success: false type: API code: INTERNAL_ERROR error: Internal server error security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer description: >- An API key from the Storiza dashboard (API & Integrations), sent as `Authorization: Bearer stz_…`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.