Hey team,
I’m curious why the checkout token isn’t included in the Order object in GraphQL Admin API?
It’s a bit confusing since you can query an order using the checkout_token in GraphQL, but the token itself isn’t visible on the Order object.
The checkout token shows up in other places like checkout extensions, Web Pixels API, webhooks, and obviously the REST API. It’s the only consistent way to link a checkout session to an order.
Hey @Patrick_Jakubik, the token is showing as deprecated so that would be the short answer on why it’s not in the graphql order object.
You’ve raised a good point though on how this is available in other places so it would be valuable on the order to help with linking checkout sessions to orders.
Some of this information may be available in the customerJourneySummary, however that may not have all that you need.
Would you be able to expand a bit on how you’re using this field and where it will make it easier to include it back in Graphql and any workarounds you have to go through with it not there? I want to be sure I share that feedback with our team without any missing context.
Hey Kyle,
in the checkout extension environment, the checkout token is the only identifier available, which we send with our requests as the checkout session ID. When merchants report issues, we rely on this token to match the order and access relevant logs for that specific checkout session. I believe deprecating checkout tokens on the order object would be a mistake.
