Hey folks,
I recently noticed that we have few mutations related to shipping packages, such as:
Yet, there is no query to list shipping packages. Could that be added? Thanks a lot!
Hi Patrick,
I’ve passed this feature request on to the relevant product team - thanks for flagging this!
1 Like
Is there any update on this? This seems like a major gap! Or is there a workaround?
Edit: to anybody landing here on google: you can get this out of chrome dev tools. Go to the settings page and interact with the shipping packages. Look in the the network tab and you’ll see the requests. Inside of the payload you’ll find an object that will look famililar to you if you’re doing anything with graphQL and it will contain all the packages and the gids.
thank you @Ryan_McDermott Can’t believe this doesn’t exist as a query in the GraphQL API yet, especially given there are mutations. So bizarre.
Hi, just wanted to follow up on this. We’re running into the exact same limitation.
We have mutations to update, delete, and make default (shippingPackageUpdate, shippingPackageDelete, shippingPackageMakeDefault), but no way to list or read the existing packages.
I confirmed by introspecting the full schema on API version 2026-01 — there’s no ShippingPackage object type, no query on Shop, and no REST endpoint either.
Our use case: we sync store packaging config to calculate shipping rates and generate return labels. Without a read endpoint, merchants have to manually duplicate their package data in our app.
Is there any update on this? Any workaround we might be missing?