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

# Respond to an exception

> Reply to Blend on a stuck order or prescription. The response is added to the exception's discussion and returns the exception to the Blend pharmacy team's queue. Responding does not resolve the exception; it clears once Blend resolves it or the missing data arrives. Blend's replies are sent to you with the `order.stuck_response` webhook.



## OpenAPI

````yaml /openapi-public.yml post /api/v1/exceptions/{exception_id}/responses
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}/responses:
    post:
      tags:
        - Exceptions
      summary: Respond to an exception
      description: >-
        Reply to Blend on a stuck order or prescription. The response is added
        to the exception's discussion and returns the exception to the Blend
        pharmacy team's queue. Responding does not resolve the exception; it
        clears once Blend resolves it or the missing data arrives. Blend's
        replies are sent to you with the `order.stuck_response` webhook.
      parameters:
        - name: exception_id
          in: path
          required: true
          description: >-
            Unique identifier for the exception (`exception_id` in the
            `order.stuck` webhook)
          schema:
            type: string
            format: uuid
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ExceptionResponseCreate'
      responses:
        '201':
          description: Response created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ExceptionResponse'
        '400':
          description: Missing `text`, or the exception is already resolved
        '404':
          description: Exception not found
components:
  schemas:
    ExceptionResponseCreate:
      type: object
      required:
        - text
      properties:
        text:
          type: string
          description: Response text
          example: The patient's corrected address is on the order now.
    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

````