Changelog for July 27, 2026

Catalog API — the purchaseFrame operation now accepts an optional notifications.webhook.id in the request body. When supplied, the referenced webhook is subscribed to updates for the newly created purchase and receives a notification once the purchase reaches a terminal state. The webhook must already exist for the caller’s organization (see registerWebhook).

Notifications — a new purchase resource is now supported by the Notifications API. Subscribers receive a single notification per catalog purchase when it reaches its final state (successful or failed), including the purchase identifier, its final status, and the catalog item identifiers that were delivered.