Truthound · API migrations and data contracts
Update consumer field and state contracts for documented API changes.
18 articles
Java ProtoJSON extensions: verify the approved qualified key
Separate an extension’s full identity from its short name.
Apply the version correction before testing string-coordinate storage
Do not generalize an old-version failure to current support. Admit string coordinates using a roundtrip on the actual installation.
Follow the corrected Unity Catalog URI contract for literal percent paths
Check percent-bearing locations by distinguishing URI text from the storage key it represents. Follow the correction toward UC's input and output boundary instead of repeating the withdrawn Delta fix as a remedy.
Migrating Shopify tracking numbers when the singular field overrides the array
Adding the plural tracking field is insufficient if the old singular field remains in the request.
Validating Shopify selling_plan_id without rejecting normal null values
The new webhook field carries the selling plan for subscription items. Requiring it on ordinary purchases rejects valid data.
Shopify return shipping tax: pending null is different from a finalized zero
Estimated and finalized tax have different calculation times. Reconciliation must preserve finalization state as well as amounts.
Shopify inventory reactivation: omitted quantity is not an explicit zero
When reactivation defaults change, the operational assumption that activation resets stock must change with them.
Shopify FULFILLMENT_NOT_REQUIRED: distinguish unfulfilled from nothing left to fulfill
Mapping the new status to a generic unfulfilled queue can leave orders with no remaining work in the dispatch backlog.
Shopify Metaobject values updates differ from patches that preserve omitted fields
Convenient serialization through values comes with clearing semantics. Record the intent to retain fields as a separate contract.
Shopify market relationships: restart pagination when the version changes
Stable relationship IDs do not imply stable cursors during a rebuild. Separate collection generations before accepting the hierarchy.
Shopify cancellation handoff: separate job acceptance from jobResult evidence
Acceptance of an asynchronous cancellation request is not evidence for a completion notice. Define where cancellation-specific results must be checked.
Updating multiple Shopify barcodes: an apparent addition can replace the entire set
Sending only a new value in barcodes can remove an existing identifier. Check the complete set and first-entry compatibility separately.
Shopify metafield filters: preserving errors instead of turning them into empty results
A failed filter differs from an actual absence of matches. Test response state alongside the returned dataset.
Shopify legalEntityId: testing cross-shop consolidation without merging unknown entities
Distinguish shop-scoped IDs from organization-level legal-entity IDs, and do not merge nulls into a single company.
Shopify local-currency gift cards: testing issuance settings against redemption strategy
Before comparing amounts in a multi-currency experiment, verify the issuance-currency and redemption-policy combination fixed at creation.
Shopify marketing engagements: testing cumulative-to-delta migration without double counting
Changing a mode flag can turn a cumulative total into a new increment. Connect the last approved total with the first emitted delta at the transition.
Shopify DraftOrderLineItem weight: carrying the unit through the grams migration
A field-name migration is also a unit-contract migration. Normalize the new value and unit together before comparing the business weight.
Shopify canceled receiving: reconciling the meaning of totalReceivedQuantity
When testing the new receiving state, separate status totals so received is not mistaken for the quantity that physically arrived.
