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

# Get Change Messages

> Get Change Messages



## OpenAPI

````yaml /openapi/openapi_commerce.json get /commerce/callofforders/{callOffOrderId}/changemessages
openapi: 3.0.1
info:
  description: |-
    <div id="overview_COMMERCE">
                <h2>COMMERCE</h2>
                <p>The Commerce API interacts with the commerce entities of your tenant, including shoppers's active shopping
                    carts, checkouts, submitted orders, wishlists, and returns as well as B2B quotes.</p>
                <p>Use the <strong>Carts</strong> resource to manage storefront shopping carts as shoppers add and remove items for purchase.
                    Each time a shopper's cart is modified, the Carts resource updates the estimated total with any
                    applicable
                    discounts.</p>
                <p>Use the <strong>Channels</strong> and <strong>Channel Groups</strong> resources to manage the channels a company uses to create logical
                    commercial business divisions based on region or types of sales, such as "US Online," "Amazon," or "EMEA
                    Retail."
                    All orders include a channel association that enables the company to perform financial reporting for
                    each defined channel.
                    Because channels are managed at the tenant level, you must associate all the tenant's sites with a
                    channel. Sites that do not
                    have a defined channel association cannot successfully submit orders.</p>
                <p>Use the <strong>Checkouts</strong> resource to track a shopper's order items and their intended destinations on sites that
                    have the multiple shipment feature enabled.</p>
                <p>Use the <strong>Orders</strong> resource to manage all components of order processing, payment, and order-level
                    fulfillment.</p>
                <p>Use the <strong>Quotes</strong> resource to support B2B functionality by managing order quotes, similar to wishlists.</p>
                <p>Use the <strong>Returns</strong> resource to manage returned items that were previously fufilled. Returns can include any
                    number of items associated with an original
                    order. Each return must either be associated with an original order or a product definition to represent
                    each returned item.</p>
                <p>Use the <strong>Wish Lists</strong> resource to manage the shopper wish lists of products associated with a customer
                    account. Although customer accounts are managed at the tenant
                    level, the system stores shopper wish lists at the site level. This enables the same customer to have
                    wish lists for each of a merchant's sites. The <strong>Wish List Items</strong>
                    resource allows you to manage the individual items in a wish list.</p>
            </div>
  title: Cart/Checkout/Quote
  version: 0.0.1
servers:
  - description: Kibo Base URL
    url: '{baseUrl}/api'
    variables:
      baseUrl:
        default: https://t1000000.sb.usc1.gcp.kibocommerce.com
        description: Base URL
security:
  - bearerAuth: []
paths:
  /commerce/callofforders/{callOffOrderId}/changemessages:
    get:
      tags:
        - CallOffOrder
      summary: Get Change Messages
      description: Get Change Messages
      parameters:
        - in: path
          name: callOffOrderId
          required: true
          schema:
            type: string
        - in: query
          name: startIndex
          schema:
            default: 0
            format: int32
            type: integer
        - in: query
          name: pageSize
          schema:
            default: 20
            format: int32
            type: integer
        - description: limits which fields are returned in the response body
          in: query
          name: responseFields
          schema:
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CallOffOrderChangeMessageCollection'
            text/json:
              schema:
                $ref: '#/components/schemas/CallOffOrderChangeMessageCollection'
            text/plain:
              schema:
                $ref: '#/components/schemas/CallOffOrderChangeMessageCollection'
          description: OK
components:
  schemas:
    CallOffOrderChangeMessageCollection:
      description: Paged result for Call-Off Order change-message queries.
      properties:
        items:
          description: Page of change messages matching the query.
          items:
            $ref: '#/components/schemas/CallOffOrderChangeMessage'
          nullable: true
          type: array
        pageSize:
          description: Maximum number of records per page.
          format: int32
          type: integer
        startIndex:
          description: Zero-based index of the first record in this page.
          format: int32
          type: integer
        totalCount:
          description: Total number of matching messages across all pages.
          format: int32
          type: integer
      type: object
    CallOffOrderChangeMessage:
      description: Audit trail entry for Call-Off Order lifecycle events.
      properties:
        body:
          description: Human-readable description of what changed.
          nullable: true
          type: string
        callOffOrderId:
          description: Identifier of the parent call-off order this message belongs to.
          nullable: true
          type: string
        createBy:
          description: User who triggered the change.
          nullable: true
          type: string
        createDate:
          description: Timestamp when the change was recorded.
          format: date-time
          type: string
        id:
          description: System-generated change message identifier.
          nullable: true
          type: string
        identifier:
          description: "Optional identifier of the specific sub-entity that changed\r\n(e.g. line id)."
          nullable: true
          type: string
        newValue:
          description: New value when the change represents a single-field mutation.
          nullable: true
          type: string
        oldValue:
          description: Prior value when the change represents a single-field mutation.
          nullable: true
          type: string
        siteId:
          description: Site identifier.
          format: int32
          type: integer
        subject:
          description: Subject of the change (e.g. "status", "line.status").
          nullable: true
          type: string
        tenantId:
          description: Tenant identifier.
          format: int32
          type: integer
      type: object
  securitySchemes:
    bearerAuth:
      bearerFormat: JWT
      description: JWT Authorization header using the Bearer scheme.
      scheme: bearer
      type: http

````