I might be late to the game on this one. Hopefully it’s an easy answer.
I’m porting from REST to GraphQL and I’m discovering that REST returns more data than is available in GraphQL (or I’m not understanding GraphQL well enough)
I don’t think this is you not understanding well enough - looks like you’re right. At this point I can only recommend using REST when you need to get those fields, but I’ll ask around internally here and see if we can get those added.
Just wanted to follow up on this with some additional information - I tracked down the phone number, it was hidden under the shop’s billingAddress. Here’s an example query that can grab that for you :
{
shop {
name
myshopifyDomain
billingAddress {
id
phone
}
}
}
However, the ‘shop_owner’ isn’t available right now - we’re looking into rectifying that as we speak.
I too am looking for shop_owner which was available in REST API but surprisingly missing from GraphQL. It has been several months since this issue has been brought to notice.. Any update on this?
The shop owner information isn’t available via GraphQL publicly right now because the way that it is used surfaces some fields that should not be available in a public API. This is still a work in progress, but please continue to check in here for any updates and I’ll do my best to let you keep you both posted.
Is there any chance you guys could get this added to theGraphQL API? It would be helpful for people that need to do pagination and bulk queries for lists larger than 250 since you have to build your own throttle using the REST API, but don’t have to with GraphQL.