2026

The Lead Time API now returns a typed error field on 200 responses when a schedule cannot be calculated. Previously, consumers had to infer failure from null nextShipDate and businessDaysToShip fields; now those nulls are accompanied by an error object with a machine-readable code and a human-readable message.

Error codes: 1 = general failure (contact customer service), 2 = unavailable for this part, 3 = supply constraint.

A new 204 response was also added for cases where no schedule data exists for a part at all (distinct from a calculated-but-failed 200).

What to check: if you were checking for null nextShipDate to detect "no schedule," also check error — it now carries the reason. Handle 204 as a distinct "no data" case.

See the Lead Time Reference for the full schema.

V3 improved the underlying paging mechanism for significantly faster traversal of the full catalog. V1 is deprecated — remaining users will be notified before it's removed. V2 deprecated virtualStockQuantity in favor of stockQuantity.

What to do: update the endpoint path from /v1/ or /v2/ to /v3/. Review the response for the stockQuantity and minimumOrderQuantity fields, and confirm your paging logic follows V3's startAfterPart behavior — leave it empty for the first page, then pass the last part number from the previous page's response to continue.

See the Catalog V3 Reference for the full endpoint list, or the Catalog overview for a quick start.