API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-126 · API endpoints & versions

Zendesk Assets API changes purchase_cost from a number to an amount-and-currency object

From 6 August 2026, Zendesk Assets API responses return purchase_cost as an object containing amount and currency rather than a plain numeric value.

ZendeskAssets APIpurchase_costresponse schemabreaking change

Previous state

The purchase_cost field returned a plain numeric value.

Current state

The purchase_cost field returns an object with separate amount and currency values.

Who needs to care

Integrations that deserialize, validate, store or calculate with the Assets API purchase_cost field as a number.

What to do

Update response models, schema validators, persistence and downstream calculations to handle the amount-and-currency object before 6 August 2026.

What the source does not prove

This is a field-level response-schema change in the Assets API; it does not remove the asset object or establish changes to unrelated cost fields.

Lifecycle history

Dated event sequence

  1. Breaking change announced

    Zendesk documented the new purchase_cost response shape.

  2. New response contract effective

    purchase_cost changes from a numeric value to an amount-and-currency object.

Evidence ledger

First-party sources

  1. 01
    Zendesk Developer — Zendesk API changelog

    Official API changelog · 2026-07-06

    Open official source ↗