> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orgo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Type text

> Type a string on the computer keyboard, one character at a time.

Types text on the computer keyboard. Each character is sent as an individual keystroke, so unicode characters and printable symbols are supported.

## Path parameters

<ParamField path="id" type="string" required>
  Computer ID (UUID). An `instance_id` is not accepted here and fails with `500`.
</ParamField>

## Query parameters

<ParamField query="screen" type="string">
  Which [screen](/api-reference/screens/list) to type on. Optional. Omit it to
  act on the screen the computer booted with. An unknown id returns `404` rather
  than falling back to the default screen. A Windows computer ignores this
  parameter.
</ParamField>

## Body parameters

<ParamField body="text" type="string" required>
  Text to type. Unicode is supported. Nothing checks that it is present:
  omitting it types the empty string and still returns `200` (with
  `text_length: 0` on Linux), so a body that lost its `text` looks like a
  success.
</ParamField>

<ParamField body="delay_ms" type="integer" default="12">
  Delay between keystrokes, in milliseconds. Optional. Omitting it, or sending
  `0`, uses 12. Lower values type faster; higher values help with inputs that
  drop fast keystrokes. A Windows computer refuses this field with `400`.
</ParamField>

<Note>
  The API waits at most 30 seconds for the computer to finish typing. The text
  takes about `delay_ms` per character, so at the default of 12 ms anything over
  roughly 2,500 characters returns `503` with `code: "ECONNABORTED"`, and the
  text may be only partly typed. Split long text into several requests.
</Note>

<Note>
  A Windows computer ignores `?screen=` and accepts only `text` in the body. Any
  other field, including `delay_ms`, returns `400`, and so does `text` longer
  than 20,000 bytes. A successful response is `{"ok": true}`.
</Note>

## Response

<ResponseField name="success" type="boolean">
  Always `true` on a `200`. A failed keystroke is an error status.
</ResponseField>

<ResponseField name="action" type="string">
  Always `type`.
</ResponseField>

<ResponseField name="details" type="object">
  Carries `text_length`, the length of the typed text in **bytes**, not
  characters. A non-ASCII character counts as more than one.
</ResponseField>

## Example

<CodeGroup>
  ```bash cURL theme={null}
  curl -X POST https://www.orgo.ai/api/computers/$COMPUTER_ID/type \
    -H "Authorization: Bearer $ORGO_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"text": "Hello, world!"}'
  ```

  ```python Python theme={null}
  import requests

  requests.post(
      f"https://www.orgo.ai/api/computers/{computer_id}/type",
      headers={"Authorization": f"Bearer {api_key}", "Content-Type": "application/json"},
      json={"text": "Hello, world!"}
  )
  ```

  ```javascript JavaScript theme={null}
  await fetch(`https://www.orgo.ai/api/computers/${computerId}/type`, {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${apiKey}`,
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({ text: 'Hello, world!' })
  });
  ```
</CodeGroup>

### Response

```json theme={null}
{
  "success": true,
  "action": "type",
  "details": { "text_length": 13 },
  "error": null,
  "error_type": null
}
```

<Tip>
  Use [Press key](/api-reference/computers/key) for special keys like Enter, Tab, or keyboard shortcuts.
</Tip>

## Errors

| Status | Meaning |
| - | - |
| `400` | The computer has no VM attached: `{"error": "Desktop instance not available"}`. Also returned by the computer agent when `text` is not a JSON string. A Windows computer also returns it for any field other than `text` or for `text` over 20,000 bytes, as `{"error": "Request failed with status code 400"}` with `upstream_status: 400`. A missing `text` is **not** a `400`: it is a `200` that types nothing. |
| `401` | Invalid API key: `{"error": "Invalid API key"}`. A request with no `Authorization` header returns `{"error": "Authentication required"}`. Access failures also return `401` on this endpoint, not `403`: `{"error": "You do not have access to this workspace."}` when you are neither the owner nor a member of the computer's workspace, `{"error": "This workspace is view-only. Ask the owner for write access (workspace_read_only)."}` for a view-only member, and `{"error": "This API key cannot access this workspace (workspace_scope_mismatch)."}` for a workspace-scoped key used outside its workspace. A server-side fault while verifying the credential also returns `401` here, with `{"error": "Service temporarily unavailable. …"}`. Retry that one; the key is fine. |
| `402` | The computer was created as a free trial that is no longer active: `{"error": "Choose a plan to continue."}`. |
| `404` | No computer with this id: `{"error": "Desktop not found"}`. Also returned when `?screen=` names a screen this computer does not have. |
| `500` | The computer agent could not type the text, or the request body is not valid JSON. |
| `503` | The computer could not be reached: `{"error": "Could not reach the desktop. Try again in a moment.", "code": "ECONNREFUSED"}`. Safe to retry. A computer that never finished provisioning also returns `503`, with `{"error": "Computer not ready"}`. Text that takes longer than 30 seconds to type also lands here, with `code: "ECONNABORTED"`; it may be only partly typed, so check before retrying. |

Every failure raised after the request leaves the API layer also carries a
`request_id`. Quote it in support requests. When the computer agent itself
answered non-2xx, the body additionally carries `upstream_status`.

```json theme={null}
{
  "error": "typing text: exit status 1",
  "request_id": "9f2b7c3d-4e5f-6a7b-8c9d-0e1f2a3b4c5d",
  "upstream_status": 500
}
```


## OpenAPI

````yaml POST /computers/{id}/type
openapi: 3.1.0
info:
  title: Orgo API
  description: >-
    Launch cloud computers that AI agents can control and interact with. Create
    workspaces, provision computers, and control them programmatically.
  version: 2.0.0
  contact:
    name: Orgo Support
    email: spencer@orgo.ai
    url: https://orgo.ai
servers:
  - url: https://www.orgo.ai/api
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Account
    description: >-
      Account capacity: how many computers an account may run, and adding or
      giving back more.
  - name: Clients
    description: >-
      Run Orgo for your clients from your own app: a workspace and scoped key
      each, billed to you or to them.
  - name: Workspaces
    description: Organize computers into named workspaces
  - name: Computers
    description: Provision and manage virtual computers
  - name: Computer Lifecycle
    description: Start, stop, and restart computers
  - name: Computer Actions
    description: Control mouse, keyboard, and execute commands
  - name: Screens
    description: >-
      More than one desktop on a single computer. Each screen is its own X
      server with its own cursor and window manager, so an agent working on one
      cannot disturb another.
  - name: Files
    description: Upload and download files
  - name: Templates
    description: Author, build, and launch reproducible computers from templates
paths:
  /computers/{id}/type:
    post:
      tags:
        - Computer Actions
      summary: Type text
      description: Types text on the computer keyboard, one keystroke per character.
      operationId: typeText
      parameters:
        - name: id
          in: path
          required: true
          description: Computer ID
          schema:
            type: string
        - name: screen
          in: query
          required: false
          description: >-
            Which screen to act on. Omit for the boot screen. An unknown id
            returns 404 rather than falling back.
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TypeRequest'
            example:
              text: Hello, world!
      responses:
        '200':
          description: >-
            Text typed. `details.text_length` is the length in bytes, not
            characters.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ActionResponse'
              example:
                success: true
                action: type
                details:
                  text_length: 13
                error: null
                error_type: null
        '400':
          description: >-
            The computer has no VM attached, or `text` is not a JSON string. A
            missing `text` is not a `400`: it is a `200` that types nothing.
          content:
            application/json:
              schema:
                anyOf:
                  - $ref: '#/components/schemas/Error'
                  - $ref: '#/components/schemas/UpstreamError'
              examples:
                no-instance:
                  summary: The computer has no VM attached. Start it first.
                  value:
                    error: Desktop instance not available
                wrong-type:
                  summary: >-
                    The computer agent rejected a body field of the wrong JSON
                    type, such as `text` sent as a string
                  value:
                    error: 'invalid JSON: …'
                    request_id: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
                    upstream_status: 400
        '401':
          $ref: '#/components/responses/UnauthorizedWithAccess'
        '402':
          $ref: '#/components/responses/TrialInactive'
        '404':
          description: >-
            No computer with this id, or `?screen=` names a screen this computer
            does not have.
          content:
            application/json:
              schema:
                anyOf:
                  - $ref: '#/components/schemas/Error'
                  - $ref: '#/components/schemas/UpstreamError'
              examples:
                no-computer:
                  summary: Unknown computer
                  value:
                    error: Desktop not found
                no-screen:
                  summary: Unknown screen
                  value:
                    error: no screen "2"
                    request_id: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
                    upstream_status: 404
        '500':
          description: >-
            The computer agent could not type the text, or the request body is
            not valid JSON.
          content:
            application/json:
              schema:
                anyOf:
                  - $ref: '#/components/schemas/UpstreamError'
                  - $ref: '#/components/schemas/InternalError'
              examples:
                agent-failed:
                  summary: Rejected by the computer agent
                  value:
                    error: 'typing text: exit status 1'
                    request_id: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
                    upstream_status: 500
        '503':
          description: >-
            The computer could not be reached. Safe to retry. Also returned when
            the computer never finished provisioning. Text that takes longer
            than 30 seconds to type also lands here with `code: "ECONNABORTED"`;
            the text may be only partly typed, so check before retrying.
          content:
            application/json:
              schema:
                anyOf:
                  - $ref: '#/components/schemas/UnreachableError'
                  - $ref: '#/components/schemas/InternalError'
              examples:
                unreachable:
                  summary: Unreachable
                  value:
                    error: Could not reach the desktop. Try again in a moment.
                    request_id: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
                    code: ECONNREFUSED
                aborted:
                  summary: The API stopped waiting after 30 seconds
                  value:
                    error: Could not reach the desktop. Try again in a moment.
                    request_id: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
                    code: ECONNABORTED
                not-ready:
                  summary: The computer never finished provisioning
                  value:
                    error: Computer not ready
                    request_id: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
components:
  schemas:
    TypeRequest:
      type: object
      required:
        - text
      properties:
        text:
          type: string
          description: >-
            Text to type. Unicode is supported. Not validated: omitting it types
            the empty string and still returns `200`.
        delay_ms:
          type: integer
          default: 12
          description: >-
            Delay between keystrokes, in milliseconds. Omitted or `0`, 12 is
            used. The API waits at most 30 seconds for the typing to finish;
            longer text returns `503` with `code: "ECONNABORTED"`, and the text
            may be only partly typed.
    ActionResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Always `true` on a `200`. A failed action is an error status.
          example: true
        action:
          type: string
          description: >-
            The action performed: `click`, `mouse_move`, `drag`, `type`,
            `key_press`, `scroll`, or `wait`.
        details:
          type: object
          additionalProperties: true
          description: Echo of what was performed. Its fields depend on the action.
        error:
          type: 'null'
          description: Always `null` on a `200`.
        error_type:
          type: 'null'
          description: Always `null` on a `200`.
    Error:
      type: object
      description: >-
        The base error body. Every failure carries `error`; individual endpoints
        add the fields named in the schemas below.
      required:
        - error
      properties:
        error:
          type: string
          description: Human-readable message.
          example: Access denied
        code:
          type: string
          description: >-
            Machine-readable reason. Present on the failures that define one,
            absent otherwise.
    UpstreamError:
      type: object
      description: >-
        A failure the computer itself returned, relayed with the computer's own
        status.
      required:
        - error
        - request_id
        - upstream_status
      properties:
        error:
          type: string
          description: The message the computer returned.
        request_id:
          type: string
          description: >-
            Correlation id for this failure. The server logged the failure under
            it, so quote it in a support report.
          example: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
        upstream_status:
          type: integer
          description: >-
            The status the computer returned. Mirrors the status of this
            response.
          example: 409
    InternalError:
      type: object
      description: >-
        An unexpected failure. Retrying is reasonable; if it persists, quote
        `request_id`.
      required:
        - error
      properties:
        error:
          type: string
        request_id:
          type: string
          description: >-
            Present on failures raised by a route that talks to a computer.
            Absent on the others.
          example: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
    UnreachableError:
      type: object
      description: >-
        The computer could not be reached. The diagnostic fields, present on the
        command endpoints, say how far the request got.
      required:
        - error
        - request_id
        - code
      properties:
        error:
          type: string
          example: Could not reach the desktop. Try again in a moment.
        request_id:
          type: string
          example: 7c1e0f4a-9b2d-4a51-8f0c-2d6b1e93a4c7
        code:
          type: string
          description: >-
            The socket-level error code, or `network_error` when none was
            reported.
          example: ECONNREFUSED
        vm_status:
          type:
            - string
            - 'null'
          description: The computer's recorded status when the request failed.
        desired_status:
          type:
            - string
            - 'null'
          description: >-
            The status the computer was being driven towards, when one was
            recorded.
        host_reachable:
          type:
            - boolean
            - 'null'
          description: Whether the host running the computer answered.
        desktop_api_reachable:
          type:
            - boolean
            - 'null'
          description: Whether the computer's own API answered.
        hint:
          type: string
          description: What to do next, given the two reachability results.
  responses:
    UnauthorizedWithAccess:
      description: >-
        No usable credential, or an access check failed. This endpoint runs its
        workspace access checks during authentication, so it answers a missing
        membership, view-only access, or a key scoped to another workspace with
        `401`, not `403`. A server-side fault while verifying the credential
        also returns `401`, with a `Service temporarily unavailable` message.
        Retry that one; the key is fine.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          examples:
            invalid-key:
              summary: The key is not one of yours
              value:
                error: Invalid API key
            no-credential:
              summary: No key and no session
              value:
                error: Authentication required
            no-access:
              summary: Not the owner or a member of the workspace
              value:
                error: You do not have access to this workspace.
            view-only:
              summary: View-only member, and the request changes something
              value:
                error: >-
                  This workspace is view-only. Ask the owner for write access
                  (workspace_read_only).
            scope-mismatch:
              summary: The API key is scoped to another workspace
              value:
                error: >-
                  This API key cannot access this workspace
                  (workspace_scope_mismatch).
            service-unavailable:
              summary: Server-side fault while verifying the credential. Retry.
              value:
                error: >-
                  Service temporarily unavailable. The database is not accepting
                  requests. Retry shortly.
    TrialInactive:
      description: >-
        The computer is a free trial computer whose trial is no longer active,
        or it is paid for by its own subscription or dedicated purchase and that
        payment has lapsed.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          examples:
            trial:
              summary: Trial no longer active
              value:
                error: Choose a plan to continue.
            payment:
              summary: The computer's own payment has lapsed
              value:
                error: Manage this computer’s payment in Account → Usage.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: API key authentication. Get your key at orgo.ai/workspaces

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.