The Shopify connector now offers a choice of API types: HTTP-based and GraphQL. In addition to the GraphQL migration topics for the deprecated product-related REST APIs, the answers to these frequently asked questions will provide additional context for customers new to these Shopify endpoints.
Q1. My current Shopify HTTP (or REST) connection still seems to be working fine. Why should I change to GraphQL? How do you recommend proceeding?
A1. As noted in communication from Shopify and Celigo, Shopify is ending support for REST APIs over time, in favor of GraphQL APIs. The prebuilt GraphQL API type connection will ensure that your flows continue to work correctly in advance of the deprecation date.
We advise that you create a GraphQL API type connection, as soon as possible, and then authenticate it. The new connector will not consume an additional endpoint in your subscription, even if you have multiple stores in Shopify.
Then, build new flows with your Shopify GraphQL connector to reproduce the same business logic, selecting the corresponding endpoints in your flow steps (such as exports and imports), using the Simple or GraphQL view. You do have to enter the GraphQL query in each Query setting, and you can rely on Celigo AI to generate the queries. Test the new flows; when they’re running as expected, enable them and disable the HTTP-based flows.
Alternatively, you can create a universal connection to Shopify.
It is possible – though not recommended – to update an existing Shopify HTTP connection to use the GraphQL API type, which also requires you to re-authenticate your connection. When you open your flow, the connection is updated to GraphQL; however, the flow steps will still appear in the connection’s former HTTP view. In this case, you must make several changes to migrate the steps for your flow to work.
Q2. If I create another prebuilt Shopify connection for the GraphQL API type, but I already have a prebuilt Shopify HTTP connection, do I have to purchase an additional endpoint?
A2. No. Since GraphQL and HTTP are just API types, they belong to the same prebuilt Shopify connector. You can create any number of connections without reducing your endpoints.
However, if you want to connect to Shopify using a universal connector, it will reserve an endpoint – or you must purchase an additional endpoint if it exceeds your entitlements.
Q3. I already migrated my Products and Variants to GraphQL by switching to HTTP view and writing queries in the HTTP body. Do I need to do anything else?
A3. If you followed this document to move to GraphQL and your flows are running fine, you can leave them as is.
See Q1, above, if you are interested in creating a Shopify connector by selecting the GraphQL API type and rebuilding your flows. For detailed information, see how to Set up a Shopify GraphQL connection and build flows.
Q4. I still have my Products and Variants in HTTP. Considering Shopify will deprecate and migrate to GraphQL, what should I do?
A4. Create a Shopify connection by choosing the GraphQL API type, authenticate the connection, and recreate your flows, as outlined in Q1.
A5. No. Once a connection is chosen, you won’t have the option to switch between HTTP and GraphQL from a flow step (such as a listener or import). You can either close the flow step and build a replacement for the other API type, or refresh the flow step before saving it.
A6. Currently, Celigo supports the GraphQL Admin API (this allows developers to programmatically access and manage a Shopify store’s data using GraphQL. It's the modern alternative to the REST Admin API and provides more efficient and flexible querying, especially when working with nested or related data).
In the upcoming release, we have plans to expand to other Shopify supported GraphQL endpoints.
A7. For support, please reach out to the Celigo Customer Success team or visit the Celigo Help Center for documentation and community assistance.