> ## 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.

# Get Care Job

> Status plus the patient-visible audit trail. `status` moves from
pending to approved, declined, or expired, then from approved to
executed or failed once Arlo's care team completes the action. While
pending the response carries the `approvalUrl` for the user.




## OpenAPI

````yaml api-reference/openapi.yaml GET /api/care-jobs/{id}
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 orders (read-only; Photon Health fulfills them)
  - name: Health Records
    description: The user's connected insurance and health records (US)
  - name: Care Pricing
    description: Free price transparency under the user's plan (US)
  - name: Care Jobs
    description: >-
      Real-world care actions Arlo's care team executes after the patient
      approves (US)
  - name: Payment
    description: Billing and pay-per-use payment management
  - name: Webhooks
    description: Webhook registration and status
paths:
  /api/care-jobs/{id}:
    get:
      tags:
        - Care Jobs
      summary: Check a care job
      description: |
        Status plus the patient-visible audit trail. `status` moves from
        pending to approved, declined, or expired, then from approved to
        executed or failed once Arlo's care team completes the action. While
        pending the response carries the `approvalUrl` for the user.
      operationId: getCareJob
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: The jobId returned when the job was created
      responses:
        '200':
          description: Care job status and audit trail
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CareJobDetail'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    CareJobDetail:
      type: object
      properties:
        jobId:
          type: string
        jobType:
          type: string
        tier:
          type: string
        status:
          type: string
          enum:
            - pending
            - approved
            - declined
            - expired
            - executed
            - failed
        sheet:
          type: object
          properties:
            title:
              type: string
            subtitle:
              type: string
        approvalUrl:
          type: string
          format: uri
          description: Present only while pending
        approvedViaLabel:
          type:
            - string
            - 'null'
          description: How the user verified, once approved
        grantId:
          type:
            - string
            - 'null'
          description: The single-use grant the care team executes under, once approved
        expiresAt:
          type:
            - integer
            - string
        audit:
          type: array
          description: The patient-visible audit trail, who did what and when
          items:
            type: object
            properties:
              actor:
                type: string
              label:
                type: string
              meta:
                type: object
              at:
                type:
                  - integer
                  - string
    Error:
      type: object
      description: Error response
      properties:
        error:
          type: string
          description: Error code
        reason:
          type: string
          description: Human-readable explanation
        code:
          type: string
          description: Detailed error code
  responses:
    BadRequest:
      description: Invalid request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    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

````