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

# Send a follow-up message to a session

> Continues the session with a new prompt on the same transcript. The
follow-up runs on the session's phone (for an agent's session, the
phone the agent has now). If the session is still running, the
follow-up is queued behind it (`queued: true`) and runs when the
current run ends. Continuing a finished session is allowed.

Send an `Idempotency-Key` header to make retries safe: the same key
attaches to the original follow-up instead of sending a second one.

Workspace scope: `workspaceId` in the body, otherwise the workspace
bound to the API key.




## OpenAPI

````yaml /api-reference/openapi.yaml post /v1/sessions/{id}/continue
openapi: 3.1.0
info:
  title: Lusor API
  version: 0.1.0
  description: |
    Run AI agents on real phones, or drive a phone directly with
    deterministic actions.

    ## Authentication

    Every `/v1/*` endpoint except `GET /v1/health` requires an API key.
    Create one in the Lusor dashboard under **Settings → API Keys**. A key
    is shown once and is bound to one workspace. Revoking it there stops it
    working immediately.

    Send it in either header:

    - `X-Api-Key: <your API key>`
    - `Authorization: Bearer <your API key>`

    Because a key is bound to its workspace, `workspaceId` query and body
    parameters are optional for API-key callers. A request that names a
    different workspace returns an opaque `404`.

    ## Runs

    Use `POST /v1/agents/{id}/turns` to start or continue an agent run.
    Read the run under `/v1/sessions/{id}`; poll
    `GET /v1/sessions/{id}/status` or `GET /v1/sessions/{id}/events` for
    progress.

    ## Errors

    Errors are JSON: `{ "error": "<code>", "message": "<text>" }`. A
    request that fails validation returns `400` in one of two shapes,
    depending on the endpoint: `{ "error": "validation_error", "details":
    { ... } }` (direct phone control actions, for example), or
    `{ "error": "bad_request", "message": "<text>" }` (agent endpoints, for
    example). Branch on `error`.
  contact:
    name: Lusor
    url: https://lusor.ai
  license:
    name: Proprietary
    url: https://lusor.ai/terms
servers:
  - url: https://api.lusor.ai
    description: Production
security:
  - ApiKey: []
  - BearerAuth: []
tags:
  - name: Agents
    description: Persistent agents, the phone each one uses, and their turns (runs).
  - name: Secrets
    description: |
      Secrets saved in a workspace (passwords, sign-in details). A run uses
      them by name through `secrets`; values never travel in a request.
  - name: Sessions
    description: |
      Run records: list, inspect, stop, and read events and artifacts. Start
      a run with `POST /v1/agents/{id}/turns`, or without an agent through
      `POST /v1/workspaces/{workspaceId}/devices/{deviceId}/sessions`.
  - name: LiveView
    description: |
      View-only WebRTC live view of a session's phone: signaling, ICE
      servers, and stream control. API keys get live view only on the
      customer's own phone, not on a Lusor Phone.
  - name: Devices
    description: |
      The phones in your workspace, and reads of their current screen and
      UI tree.
  - name: DeviceVerbs
    description: |
      Direct phone control: deterministic actions (tap, swipe, type, key,
      clear, back, home, recent, screenshot, apps/start, apps/stop) and
      chains of them. On a Lusor Phone, API-key calls meter phone minutes.
  - name: Shell
    description: |
      Restricted shell escape hatch. Commands are checked against a
      denylist and audit-logged. No command output is returned.
  - name: Datasets
    description: Lists a run produced, saved as reusable Datasets.
  - name: Skills
    description: Reusable automation skills (Markdown documents).
  - name: PhoneNumbers
    description: |
      Workspace phone numbers and their stored SMS messages. Read-only for
      API keys.
  - name: Emails
    description: |
      Workspace Agent Mail addresses and stored inbound mail.
      Read-only: there is no compose, reply, or send endpoint, and message
      bodies are returned as raw plain text without HTML execution, remote
      asset fetches, or code extraction.
  - name: Workspaces
    description: The workspace an API key is bound to.
  - name: Catalog
    description: The catalog of apps that can be installed on a Lusor Phone.
  - name: Health
    description: Service health check.
paths:
  /v1/sessions/{id}/continue:
    post:
      tags:
        - Sessions
      summary: Send a follow-up message to a session
      description: |
        Continues the session with a new prompt on the same transcript. The
        follow-up runs on the session's phone (for an agent's session, the
        phone the agent has now). If the session is still running, the
        follow-up is queued behind it (`queued: true`) and runs when the
        current run ends. Continuing a finished session is allowed.

        Send an `Idempotency-Key` header to make retries safe: the same key
        attaches to the original follow-up instead of sending a second one.

        Workspace scope: `workspaceId` in the body, otherwise the workspace
        bound to the API key.
      operationId: continueSession
      parameters:
        - $ref: '#/components/parameters/SessionId'
        - $ref: '#/components/parameters/IdempotencyKey'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ContinueSessionInput'
      responses:
        '202':
          description: Follow-up accepted, dispatched or queued
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ContinueSessionResult'
        '400':
          description: |
            `bad_request`: `prompt` is missing or empty, `maxDurationSecs` is
            not a positive integer, no workspace could be resolved, or the
            session is not bound to a device.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '402':
          description: |
            `credits_exhausted`: the workspace is out of credits.
            `billing_required`: the session's Lusor Phone is not covered by
            an active paid plan.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          description: |
            The follow-up cannot run now. `agent_needs_device`: the
            session's agent has no phone attached. `recording_required`: the
            agent session started without recording; start a new turn
            instead. `device_busy`: the phone is being reset or updated.
            `trial_phone_unavailable`: the trial phone this session ran on
            is no longer available. `internet_route_inactive`: the Lusor
            Phone's Internet connection is not active yet. `device_releasing`:
            the phone is being removed from the Phone plan.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '429':
          description: >-
            `device_busy`: the phone is running a different session; stop it
            first.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Busy'
        '502':
          description: |
            `upstream_error` or `dispatch_outcome_unknown`. With
            `dispatch_outcome_unknown` the follow-up may have been accepted;
            retry with the same `Idempotency-Key`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  parameters:
    SessionId:
      name: id
      in: path
      required: true
      schema:
        type: string
      description: Session ID.
    IdempotencyKey:
      name: Idempotency-Key
      in: header
      schema:
        type: string
        maxLength: 256
      description: |
        Caller-provided key for safe retries. The same key in the same
        workspace yields the same run id, and a duplicate POST within the
        retention window returns the original run instead of starting a
        second one.
  schemas:
    ContinueSessionInput:
      type: object
      required:
        - prompt
      properties:
        prompt:
          type: string
          minLength: 1
          description: The follow-up message.
        maxDurationSecs:
          type: integer
          minimum: 1
          description: >-
            Optional cap on the follow-up run's duration, in seconds. The server
            applies its own upper bound.
        workspaceId:
          type: string
          format: uuid
          description: Optional for workspace-scoped API keys.
    ContinueSessionResult:
      type: object
      required:
        - id
        - status
        - deviceId
        - workspaceId
      properties:
        id:
          type: string
          description: The session id (unchanged).
        status:
          type: string
          enum:
            - queued
        deviceId:
          type: string
        workspaceId:
          type: string
          format: uuid
        invocationId:
          type: string
          description: |
            The follow-up's invocation. Absent when an `Idempotency-Key`
            matched a follow-up that has already run.
        queued:
          type: boolean
          description: |
            `true` when the follow-up waits behind the session's current run.
            Cancel it with `DELETE /v1/sessions/{id}/queue/{invocationId}`.
        queuedEventId:
          type: string
          description: Id of the `followup_queued` event, when `queued` is true.
    ErrorResponse:
      type: object
      required:
        - error
        - message
      properties:
        error:
          type: string
        message:
          type: string
    Busy:
      type: object
      description: |
        A `429` refusal. `device_busy` carries `currentSessionId` (the run
        holding the phone); `cap_busy` does not. Any authenticated request
        can also get `rate_limit_exceeded` when the API's request rate limit
        is exceeded; it comes with a `Retry-After` header in seconds.
      required:
        - error
      properties:
        error:
          type: string
          enum:
            - device_busy
            - cap_busy
            - rate_limit_exceeded
        currentSessionId:
          type:
            - string
            - 'null'
        message:
          type: string
  responses:
    Unauthorized:
      description: Authentication required or invalid credentials.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    NotFound:
      description: Resource not found.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: X-Api-Key
      description: Workspace API key, created in the dashboard under Settings → API Keys.
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        The same workspace API key, sent as `Authorization: Bearer <your API
        key>`.

````

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