List mapping history revisions
Traverse immutable per-item mapping revisions, including active, superseded, and previously mapped empty states.
GET/v1/catalog/items/mapping/history
Request schema: None
Success schema: CompanyItemMappingHistoryResponseV1
Documented HTTP statuses: 200, 400, 401, 403, 404, 429, 503
Contract: v1-baseline.json
Authorization
Every page is reauthorized for the represented company. History metadata remains available when HPH Item Code is withheld; association links are then omitted. Use only the continuation link returned by the service.
Request guidance
Use an optional page_size from 1 through 25. For another page, send the returned relative next link unchanged; do not add a revision watermark or expose the continuation in logs.
Parameters
| Name | In | Type | Presence | Constraints | Description |
|---|---|---|---|---|---|
company_item_id | query | string | Required | minLength 1; maxLength 255 | |
page_size | query | integer or string (int32) | Optional | minimum 1; maximum 25; pattern ^-?(?:0|[1-9]\d*)$ | |
continuation | query | string | Optional | minLength 1; maxLength 64 |
Request body
This operation has no JSON request body.
Idempotency and recovery
No idempotency key is used because history retrieval is read-only.
Response guidance
item_skey identifies the same durable Company catalog item across item-ID changes. history_availability is complete or pre_cutover_unavailable. Revision 0 never appears in history. Each entry reports an association_count of 0 or 1 and links to its immutable snapshot only when the represented Company's current license and field policy permit HPH Item Code disclosure.
Success response
No synthetic example is approved for this operation. Use the success schema and response guidance above.