> ## Documentation Index > Fetch the complete documentation index at: https://docs.arlohealth.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Conversations > Returns the user's conversations, newest activity first. The optional status filter is applied to the page `limit` returned, so raise `limit` if you filter for a rarer status. It is REST-only — the MCP `list_conversations` tool has no status parameter (it paginates with a cursor instead). ## OpenAPI ````yaml api-reference/openapi.yaml GET /api/consultations openapi: 3.1.0 info: title: Arlo Health MCP Server version: 1.0.0 description: | Healthcare infrastructure for AI agents. Everything an agent needs to act in healthcare for its user. ## Overview This server exposes two interfaces: - **MCP** (Model Context Protocol) over streamable HTTP at `/` for AI agents - **REST API** at `/api/*` for bots, skills, and direct HTTP clients Both interfaces use the same tool handlers and authentication. ## Authentication OAuth 2.1 with PKCE. All `/api/*` endpoints require a Bearer token. Discovery endpoints (no auth required): - `/.well-known/oauth-protected-resource` - `/.well-known/oauth-authorization-server` - `/.well-known/mcp.json` (MCP Server Card) ## Service Regions Care is licensed by where the patient is physically located when they request it, so every conversation carries an ISO 3166-2 `region` code. Arlo currently serves California, United States (`US-CA`); an unsupported region is refused with `REGION_NOT_SUPPORTED`, whose payload names the regions Arlo serves at that moment. contact: name: Arlo Health url: https://arlohealth.ai license: name: Proprietary url: https://arlohealth.ai/tos servers: - url: https://mcp.arlohealth.ai description: Production MCP Server security: - oauth2: - openid - profile - email - offline_access tags: - name: Discovery description: MCP and OAuth discovery endpoints (no auth required) - name: Profile description: User profile and patient information - name: Consultations description: Healthcare consultation management - name: Messaging description: Conversation messaging and media - name: Prescriptions description: Prescription and pharmacy management - name: Payment description: Billing and pay-per-use payment management - name: Webhooks description: Webhook registration and status paths: /api/consultations: get: tags: - Consultations summary: List consultations description: | Returns the user's conversations, newest activity first. The optional status filter is applied to the page `limit` returned, so raise `limit` if you filter for a rarer status. It is REST-only — the MCP `list_conversations` tool has no status parameter (it paginates with a cursor instead). operationId: listConsultations parameters: - name: limit in: query schema: type: integer default: 10 description: Maximum number of results - name: status in: query schema: type: string description: > Comma-separated status filter (e.g. "WITH_PROVIDER,MATCHING" or "IDLE"). See ConsultationStatus for valid values. Applied to the page of `limit` conversations returned. responses: '200': description: List of consultations content: application/json: schema: type: object properties: conversations: type: array items: $ref: '#/components/schemas/ConsultationSummary' total: type: integer description: Conversations in this response, not an overall count '401': $ref: '#/components/responses/Unauthorized' components: schemas: ConsultationSummary: type: object description: Summary of a conversation in list view properties: id: type: string description: Opaque conversation id title: type: string nullable: true description: Short AI-generated title; null if not yet generated status: $ref: '#/components/schemas/ConsultationStatus' region: type: string nullable: true description: >- ISO 3166-2 state/province this conversation is licensed for (e.g. US-CA) hasActiveProvider: type: boolean description: True when a provider is currently in seat on this conversation pastVisitCount: type: integer description: Number of completed provider visits on this conversation lastMessage: type: object nullable: true description: Preview of the conversation's newest message properties: type: type: string enum: - text - triage - photo - file - unknown preview: type: string description: First 100 characters of the message text fileName: type: string timestamp: type: string lastActivityAt: type: string format: date-time nullable: true description: >- Timestamp of the newest message. Sort and display "last active" on this updatedAt: type: string format: date-time nullable: true description: | Timestamp of the last status or lifecycle change. Messages do not move it, so on a busy thread it sits behind lastActivityAt. ConsultationStatus: type: string enum: - IDLE - TRIAGING - PAYMENT_REQUIRED - MATCHING - WITH_PROVIDER - EMERGENCY description: > A conversation is a continuous thread — it never "closes." There is no terminal CLOSED/CANCELED status: a finished or canceled request simply leaves the conversation IDLE with its visit history intact. - IDLE: AI-only, nothing in progress. Re-engageable — sending a message re-runs triage - TRIAGING: AI is gathering symptom information on a live request - PAYMENT_REQUIRED: Triage complete, awaiting payment confirmation (or dismissal) - MATCHING: Being matched with a healthcare provider - WITH_PROVIDER: A provider is connected (messaging is asynchronous) - EMERGENCY: Urgent care advised — user should call 911 (not re-engageable) responses: Unauthorized: description: Missing or invalid authentication content: application/json: schema: type: object properties: error: type: string needsAuth: type: boolean securitySchemes: oauth2: type: oauth2 description: OAuth 2.1 with PKCE flows: authorizationCode: authorizationUrl: /oauth/authorize tokenUrl: /oauth/token scopes: openid: OpenID Connect profile: User profile email: Email address offline_access: Refresh tokens ````