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

# End a session

> Request closure of an owned session. New API operations stop and billable use ends at recorded closure. Capacity stays occupied until cleanup is confirmed. Repeating after the session is removed may return 404; use the create receipt to confirm cleanup.



## OpenAPI

````yaml /openapi.json delete /sessions/{sid}
openapi: 3.1.0
info:
  title: Phone Harness API
  version: '2026-09-14'
  description: >-
    Public account and disposable Android session API. Open beta. Create
    responses are asynchronous; session duration includes provisioning, while
    billing begins at readiness. This specification documents the current
    supported client contract, not internal management interfaces. All example
    IDs, links, timestamps, limits, prices and digests are illustrative, not
    live credentials, measurements, or account entitlements.
  contact:
    name: Phone Harness support
    email: support@phone-harness.com
servers:
  - url: https://api.phone-harness.com
    description: Production beta
security:
  - ApiKey: []
tags:
  - name: Sessions
  - name: Phone
  - name: ADB
  - name: Account
  - name: History
  - name: Service
paths:
  /sessions/{sid}:
    delete:
      tags:
        - Sessions
      summary: End a session
      description: >-
        Request closure of an owned session. New API operations stop and
        billable use ends at recorded closure. Capacity stays occupied until
        cleanup is confirmed. Repeating after the session is removed may return
        404; use the create receipt to confirm cleanup.
      operationId: end-session
      parameters:
        - name: sid
          in: path
          required: true
          schema:
            type: string
          description: Session ID returned by POST /sessions.
      responses:
        '200':
          description: Cleanup confirmed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Release'
              example:
                released: true
                cleanup_pending: false
        '202':
          description: Closure accepted; cleanup is pending.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Release'
              example:
                released: false
                cleanup_pending: true
        '401':
          description: Bad or missing bearer credential.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Account access denied or rental access unavailable.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: No live session visible to the caller.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Unexpected service error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Release:
      type: object
      properties:
        released:
          type: boolean
          description: True only when cleanup was confirmed by this response.
        cleanup_pending:
          type: boolean
      required:
        - released
        - cleanup_pending
    Error:
      type: object
      properties:
        error:
          type: string
          description: Human-readable public error.
        code:
          type: string
          description: Present only for errors with a stable code.
        state:
          type: string
        unsupported:
          type: boolean
        outcome:
          type: string
          enum:
            - unknown
            - installed
        id:
          type: string
          description: Session ID if a create receipt exists.
        request_key:
          type: string
        cleanup_complete:
          type: boolean
        balance_cents:
          type: integer
        session:
          type: string
        session_limit:
          type: integer
        active_session_count:
          type: integer
        available_session_slots:
          type: integer
      required:
        - error
  securitySchemes:
    ApiKey:
      type: http
      scheme: bearer
      description: >-
        Phone Harness account API key (pck_…). The dashboard may use a Clerk
        session JWT with the same header. Never put an account key in a URL.

````