Missing Order Fields in Shopify GraphQL API

Partner Discussions
1

Hi Shopify Community and Support,

We’re a Shopify Partner currently migrating one of our apps, which uses the Shopify Order API, from REST to GraphQL. We’re doing this to align with the platform’s evolving standards.

During this transition, we’ve noticed that certain fields that are available in the REST Order API response are currently missing from the GraphQL Order API response. The specific fields we’re looking for are:

  • cart_token
  • checkout_token
  • checkout_id
  • client_details

To maintain full functionality for our merchants, we’re temporarily relying on the REST API for these particular fields. We’re also planning to utilize the order creation webhooks, as they currently include this data and match the REST API structure.

We’d appreciate any insights you could provide regarding the future availability of these fields:

  1. Are there plans to include cart_token, checkout_token, checkout_id, and client_details in the GraphQL Order API response in future updates?
  2. Is there a roadmap for deprecating the current order creation webhook, or changing its structure to align with the GraphQL API response?
  3. If the order creation webhook does change to match GraphQL, will these specific fields (cart_token, checkout_token, checkout_id, client_details) continue to be part of the webhook payload?
1 Like
2

Hey @Ramesh_Yoha!

Looking at the specific fields you mentioned, cart_token and checkout_token are actually marked as deprecated in the REST API documentation, so they’ll likely be removed from webhooks as well at some point.

For client_details, this data is actually available in GraphQL through the customerJourneySummary field on the Order object, which provides much richer customer journey information including UTM parameters, referrer data, and conversion timing.

I’m not seeing checkout ID on our oldest REST version. Is this field nested within a different object?

I’d love to dig deeper into your specific use cases for these fields though. Can you share a bit more about how you’re currently using these fields in your app? With that context, we can look at the best GraphQL alternatives that’ll get you as close as possible to your current functionality.