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

# Get an exception

> Retrieve a single exception on a stuck order or prescription. Use the `exception_id` from the `order.stuck` webhook.



## OpenAPI

````yaml /openapi-public.yml get /api/v1/exceptions/{exception_id}
openapi: 3.0.3
info:
  title: Blend API
  version: 1.0.0
  description: API for Blend
servers:
  - url: https://api.byblend.com
    description: Blend production server
security:
  - bearerAuth: []
tags:
  - name: Orders
    description: Order management endpoints
  - name: Patients
    description: Patient management endpoints
  - name: Reports
    description: Reporting endpoints
  - name: Products and Materials
    description: Product catalog and inventory endpoints
  - name: Electronic Prescriptions
    description: Electronic prescription management endpoints
  - name: Exceptions
    x-group: Exceptions (Stuck Orders)
    description: Stuck order and prescription exceptions, and responses to them
  - name: Prescriptions
    description: Prescription management endpoints
  - name: Authentication
    description: Authentication endpoints
  - name: Notifications
    description: User management endpoints
  - name: Prescribers
paths:
  /api/v1/exceptions/{exception_id}:
    get:
      tags:
        - Exceptions
      summary: Get an exception
      description: >-
        Retrieve a single exception on a stuck order or prescription. Use the
        `exception_id` from the `order.stuck` webhook.
      parameters:
        - name: exception_id
          in: path
          required: true
          description: Unique identifier for the exception
          schema:
            type: string
            format: uuid
        - name: include_responses
          in: query
          required: false
          description: Include the exception's responses (oldest first) as `responses`
          schema:
            type: boolean
            default: false
      responses:
        '200':
          description: Successful response with exception details
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Exception'
        '404':
          description: Exception not found
components:
  schemas:
    Exception:
      type: object
      properties:
        id:
          type: string
          format: uuid
          description: >-
            Unique identifier for the exception. Sent as `exception_id` in the
            `order.stuck` webhook.
          example: 0227d1e5-ba9a-42b5-8fe2-38882aa65708
        entity_type:
          type: string
          enum:
            - order
            - prescription
          description: Whether the exception is on an order or on a prescription
          example: order
        entity_id:
          type: string
          format: uuid
          description: ID of the order or prescription the exception is on
          example: b658f16f-819c-4503-aede-bd555fc4ebfb
        exception_reason:
          type: string
          enum:
            - prescriber_data
            - patient_data
            - clinical_issue
            - patient_readiness
            - prescription_expired
            - prescription_missing
            - no_fills_remaining
            - order_data
            - address
            - order_too_early
            - duplicate_active_order
          description: Why the order or prescription is stuck
          example: address
        exception_reason_display:
          type: string
          description: Human-readable version of `exception_reason`
          example: Address Update Required
        exception_description:
          type: string
          nullable: true
          description: Detail from Blend on what is needed
          example: Address could not be verified by the carrier
        is_active:
          type: boolean
          description: >-
            `true` while the exception is blocking fulfillment; `false` once
            resolved
          example: true
        is_customer_resolvable:
          type: boolean
          description: >-
            Whether supplying data from your side is expected to clear the
            exception
          example: true
        expires_at:
          type: string
          format: date-time
          nullable: true
          description: >-
            For time-based exceptions (e.g. too early to fill), when the
            exception resolves on its own
          example: null
        created_at:
          type: string
          format: date-time
          example: '2026-09-30T17:12:00'
        resolved_at:
          type: string
          format: date-time
          nullable: true
          example: null
        resolution_reason:
          type: string
          nullable: true
          description: Why the exception was resolved
          example: null
        annotation_id:
          type: string
          format: uuid
          nullable: true
          description: ID of the exception's discussion thread
          example: 7d0f2a8c-8b4e-4c2e-9f1d-3a6b5c4d2e10
        responses:
          type: array
          description: >-
            Responses on the exception, oldest first. Only present when
            `include_responses=true`.
          items:
            $ref: '#/components/schemas/ExceptionResponse'
    ExceptionResponse:
      type: object
      properties:
        id:
          type: string
          format: uuid
          description: Unique identifier for the response
          example: 5b1f7f0e-2f6c-4c1e-9a55-0f3f4b0c9a21
        exception_id:
          type: string
          format: uuid
          description: ID of the exception this response belongs to
          example: 0227d1e5-ba9a-42b5-8fe2-38882aa65708
        text:
          type: string
          description: Response text
          example: The patient's corrected address is on the order now.
        created_at:
          type: string
          format: date-time
          description: Date and time the response was posted
          example: '2026-09-30T18:04:00'
        author:
          type: object
          properties:
            first_name:
              type: string
              example: Charlie
            last_name:
              type: string
              example: Customer
            type:
              type: string
              enum:
                - blend
                - customer
                - system
              description: >-
                Who wrote the response: Blend pharmacy staff, a user on your
                account, or the system
              example: customer
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````