Shopify Python API and Future GraphQL-Only Support

[NavidBecause]

Description

Shopify has announced plans to deprecate the REST API in favor of GraphQL-only support. However, the shopify_python_api package still heavily relies on REST under the hood, even when using the shopify.GraphQL client.

As Shopify transitions to a GraphQL only approach, I'm wondering

• Will the Shopify Python API be updated to fully support GraphQL-only workflows?
• Are there plans to remove REST dependencies and provide an optimized GraphQL client?
• Should developers continue using this package for GraphQL, or should we start migrating to custom GraphQL clients?
• If an official GraphQL-first version is planned, is there an ETA or roadmap?

Any insights into future plans and recommendations would be greatly appreciated. Thank you so much! 🙏

[rafalpietrzakio]

Bump! I see that REST will (might) be abandoned around April. This plugin supports some GraphQL queries (GraphQL.execute(query)) so it's possible to switch and consume GraphQL here as well

[rjh336]

Hey @sle-c @Arkham - do you know the answers to the above? I think it will be important to add clarity about which parts of this package will be inoperable due to the REST API decommissioning next month

[github-actions]

This issue is stale because it has been open for 60 days with no activity. It will be closed if no further action occurs in 14 days.

[sdobbelaere]

bump

[github-actions]

This issue is stale because it has been open for 60 days with no activity. It will be closed if no further action occurs in 14 days.

[AMontagu]

bump

[cjauvin]

As a Python developer new to Shopify, I am confused by this situation. What is the status of this library, in relation to GraphQL and REST support's future?

[AMontagu]

I am not a maintener of this project. But the experience we get is the following:

• The futur of shopify is full graphql.
• This lib already support the possibility of execute graphql query
• As REST and graphql are fundamentaly different the current lib interface may not be logic anymore.

My reco is go forward and start making yor own graphql query with the client already existing in this lib and use LLM engine of you choices with the shopify doc as MCP or context to help you with that

[cjauvin]

I switched to the gql python library. IMO this library (shopify API) should have a clear warning in the README, to better explain the situation (what is there currently is not explicit enough). I imagine that it could be even possible to create yet another library that would wrap GraphQL, to offer a higher-level interface, as this one is doing? But I repeat: having this library be a high-level wrapper around a deprecated API, as well as a sub-interface to GraphQL, is too confusing.

[tulayha]

For anyone following this discussion: I ran into the same limitation (this package being REST-heavy with incomplete GraphQL support) and built a separate helper library focused purely on GraphQL.

Repo: https://github.com/tulayha/shopify-gql-helper-py
PyPI: https://pypi.org/project/shopify-gql-helper/

It’s a lightweight GraphQL-first client.

Current features:

• Pagination handling
• Throttling
• Shared sessions per store (tested in ETL scripts with parallel per-store calls holding up well)

Planned (contributions welcome):

• Bulk import
• Nested resource-level iteration

Sharing here in case it’s useful until/if this package officially shifts to GraphQL.

Note: this is read-only/ETL-focused right now; haven't tested out mutations and they may throw errors.