Hi! We are matching a checkout with an order using the checkout token and admin REST api using this endpoint /orders.json?checkout_token=${checkoutToken} . This has worked fine until recently, when suddenly some requests returned no matching orders. Checking the related order we see that the checkout token does not match the one in the original checkout. Is this a known issue, and is there a better way to do this?
Topic summary
Issue: A checkout-to-order matching process using the Admin REST endpoint /orders.json?checkout_token={token} has become unreliable. Requests that previously returned the associated order now sometimes return no results.
Technical detail: The “checkout token” is used to link a checkout session to its resulting order. In the failing cases, the order exists but its stored checkout token does not match the token from the original checkout, breaking the lookup.
Impact: This token mismatch prevents consistently correlating completed orders with their originating checkouts, disrupting post-purchase workflows.
Request for guidance: The reporter asks whether this behavior is a known issue and seeks a more reliable approach (e.g., alternative identifiers or different API methods) to associate checkouts with orders. No confirmations, workarounds, or resolutions have been provided yet; the question remains open.
1 Like