Hi there,
as a part of the REST to GraphQL migration, we are starting using this query:
{
deliveryProfiles(first: 250) {
…
}
}
But for some stores it returns the following error:
Access denied for deliveryProfiles field
However all our stores have the read_shipping permission, and it is quite strange that it works for some stores and not for others.
Here is a x-request-id example:
ce2d27ac-f753-47a9-9d76-bcff0021e14d-1736435260
Why is this happening? Please could you take a look?
I’ve run into this before, just due to a mistake in our own access scope configuration for a short period of time.
If a merchant installs while a permission isn’t asked for, you may see this.
Did you double check that this specific merchant has accepted the read_shipping scope?
Hi @Dylan,
on the one hand, I was wrong, and as you said, I have confirmed that those specific merchants have not accepted the ‘read_shipping’ permissions.
On the other hand, my confusion has been generated by the fact that this ‘read_shipping’ permission is not required for the ‘/shipping_zones.json’ REST API endpoint (which is the equivalent to the GraphQL ‘deliveryProfiles’ query according to ShippingZone - REST).
With this, my question now is: is the requirement of this permission necessary? It highly complicates the REST to GraphQL API migration.