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

# Read one of your orders by reference

> Reads one order that belongs to a brand your API key owns. It returns the same non-PHI order details as the orders list — reference, brand, offering, status, amount in minor units, currency, and timestamps. An order on a brand you do not own, or one that does not exist, both return 404 (indistinguishable, so a reference from another tenant never reveals its existence).



## OpenAPI

````yaml /openapi/public-openapi.json get /v1/account/orders/{order_ref}
openapi: 3.1.0
info:
  title: Purple API
  version: 0.0.0
servers:
  - url: https://api.dev.purplelabelmd.com
security: []
tags:
  - description: Sign a patient in and out and manage the browser session.
    name: Sessions & authentication
  - description: Run the server-driven intake questionnaire question by question.
    name: Intake
  - description: Address autocomplete for the intake flow.
    name: Addresses
  - description: Read the public status of a patient's enrollment.
    name: Enrollment
  - description: Track a client's onboarding progress.
    name: Onboarding
  - description: Read back the platform configuration stored for your brand.
    name: Brand configuration
  - description: Enable offerings for your brand and set their display copy.
    name: Offering configuration
  - description: Start and track payments for an order.
    name: Payments
  - description: Subscribe to platform events and manage delivery endpoints.
    name: Webhooks
paths:
  /v1/account/orders/{order_ref}:
    get:
      tags:
        - Payments
      summary: Read one of your orders by reference
      description: >-
        Reads one order that belongs to a brand your API key owns. It returns
        the same non-PHI order details as the orders list — reference, brand,
        offering, status, amount in minor units, currency, and timestamps. An
        order on a brand you do not own, or one that does not exist, both return
        404 (indistinguishable, so a reference from another tenant never reveals
        its existence).
      operationId: getCommerceAccountOrder
      parameters:
        - $ref: '#/components/parameters/CommerceOrderRef'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommerceAccountOrderRow'
          description: the client's order (non-PHI projection)
        '401':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/CommerceProblem'
          description: Unauthenticated — a single opaque error body — RFC 7807
        '404':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/CommerceProblem'
          description: >-
            no such order (unknown OR cross-tenant — indistinguishable) — RFC
            7807
      security:
        - apiKey: []
components:
  parameters:
    CommerceOrderRef:
      in: path
      name: order_ref
      required: true
      schema:
        pattern: ^ord_[A-Za-z0-9][A-Za-z0-9_-]*$
        type: string
  schemas:
    CommerceAccountOrderRow:
      additionalProperties: false
      description: >-
        The non-PHI view of one of your orders — a closed, minimum-necessary
        set: order reference, brand, offering, status, exact amount in minor
        units, currency, and timestamps. It never includes patient identity
        (name, email, phone, address), medical information, card data, a payment
        reference, or any secret. It reports the order; it does not move money.
      properties:
        brand_id:
          description: >-
            the client's brand this order belongs to — the account table's
            grouping/filter key
          type: string
        created_at:
          description: order creation timestamp
          format: date-time
          type: string
        currency:
          pattern: ^[A-Z]{3}$
          type: string
        offering_ref:
          description: the offering (SKU-family) this order was placed against
          type: string
        order_ref:
          type: string
        state:
          enum:
            - created
            - payment_authorized
            - paid
            - payment_failed
            - partially_refunded
            - refunded
            - disputed
            - cancelled
          type: string
        total_minor:
          description: >-
            order total, integer minor units (never a float) — money-SHAPED, not
            moved
          type: integer
        updated_at:
          description: >-
            last-modification timestamp — advances on every state change. The
            RECONCILIATION watermark: sort key + the updated_since filter
            target, so a client can catch up after a missed webhook window.
          format: date-time
          type: string
      required:
        - order_ref
        - brand_id
        - offering_ref
        - state
        - total_minor
        - currency
        - created_at
        - updated_at
      type: object
    CommerceProblem:
      description: RFC 7807 problem document (api-style-guide)
      properties:
        detail:
          type: string
        status:
          type: integer
        title:
          type: string
        type:
          type: string
      required:
        - type
        - title
        - status
      type: object
  securitySchemes:
    apiKey:
      description: 'Per-client API key (M2M). Presented as `Authorization: Bearer <key>`.'
      scheme: bearer
      type: http

````