GET api/product/GetChanges?filterCode={filterCode}&itemNo={itemNo}

Get the history product changes/notes list

Request Information

URI Parameters

Body Parameters

None.

Response Information

Resource Description

Item Type Definitions

Items - These are standalone products packaged in a single box.

• Examples include a dining chair, a complete nightstand, or even a dining set where all components are packaged together in one box.
• The contents may represent a single product or multiple pieces bundled as a complete set.

Kit Items - Products requiring multiple boxes for complete assembly or functionality.

• Examples include a dining table where the tabletop and legs are boxed separately.
• While the complete product is sold as one SKU, its components are shipped in multiple packages.

Supplement Items - Products that depend on a primary item to function, often enhancing or complementing another product.

• Examples: A dresser mirror (requires a dresser for use) or a trundle (designed to pair with a daybed).
• While sellable individually, they lack standalone utility without the corresponding main product.

Components - Single-box parts of a larger Kit Item, typically not sold or listed independently.

• Examples include the tabletop or legs of a Kit Item dining table.
• Unlike Supplement Items, Components are integral parts of a single product, not optional add-ons.

Combo Sets - Bundles of individually sellable Items curated for convenience or a cohesive design.

• Examples: A dining set combining a Kit Item table with four matching dining chairs (each chair being an Item).
• These sets simplify purchasing and ensure compatibility among the pieces.

Sellable Components - Functionally part of a larger Kit Item but capable of being sold or used on their own.

• Examples: A headboard from a multi-box bed or a standalone glass tabletop for a dining table.
• Unlike Components, Sellable Components retain functional value independently and are offered individually.

Response Formats

{
  "Error": "sample string 1",
  "Message": "sample string 2",
  "Items": [
    {
      "ItemNo": "sample string 1",
      "ChangeAction": "sample string 2",
      "ChangeDescription": "sample string 3",
      "DateChange": "2024-12-26T20:19:55.3559479-08:00"
    },
    {
      "ItemNo": "sample string 1",
      "ChangeAction": "sample string 2",
      "ChangeDescription": "sample string 3",
      "DateChange": "2024-12-26T20:19:55.3559479-08:00"
    }
  ]
}

<ChangeHistory xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/CoasterAPI.Products">
  <Error>sample string 1</Error>
  <Items>
    <ChangeHistory.Item>
      <ChangeAction>sample string 2</ChangeAction>
      <ChangeDescription>sample string 3</ChangeDescription>
      <DateChange>2024-12-26T20:19:55.3559479-08:00</DateChange>
      <ItemNo>sample string 1</ItemNo>
    </ChangeHistory.Item>
    <ChangeHistory.Item>
      <ChangeAction>sample string 2</ChangeAction>
      <ChangeDescription>sample string 3</ChangeDescription>
      <DateChange>2024-12-26T20:19:55.3559479-08:00</DateChange>
      <ItemNo>sample string 1</ItemNo>
    </ChangeHistory.Item>
  </Items>
  <Message>sample string 2</Message>
</ChangeHistory>