Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REST Product APIs Being Deprecated in February 2025 #191

Open
glevineLeap opened this issue Nov 19, 2024 · 6 comments
Open

REST Product APIs Being Deprecated in February 2025 #191

glevineLeap opened this issue Nov 19, 2024 · 6 comments

Comments

@glevineLeap
Copy link

Don't know if this repo is still actively monitor or maintained.

The REST Product APIs are being deprecated in February with the rest of the REST APIs to follow later in the year. The tap relies on the ShopifyAPI package and as yet I haven't seen any indication that they intend to support the existing Product model on GraphQL with the same interface: Shopify/shopify_python_api#745.

Is there a plan for supporting the product stream beyond February and what is the larger roadmap for the rest of the tap given the impending deprecation of the remaining REST endpoints?

@glevineLeap
Copy link
Author

There's a response on the linked issue confirming that the resources used by the tap are not going to continue to be supported by the official library:

Response from Shopify Developer Support:

James here from the Developer Support team at Shopify. John has caught me up to speed on your issue with your questions about the Python pyactiveresource library.

My team does not support our public libraries, but I notice that the last commit was over 2 years ago, and their philosophy statement outlines how it aims to provide a "wrapper object-relational mapping for REST web services", but our REST Admin API's as a legacy API in our latest quarterly release.

I reached out to our developers who work on the Python API library to see if I could get some clarification, and they confirmed that they we do not currently plan to map the existing GraphQL Admin client to use that resource based syntax. Their recommendation is to migrate to using GraphQL queries and mutations in order to move off of the REST Admin API for all of the current users of the client libraries in all languages.

Our dev docs also have some resources on how to migrate from REST to GraphQL, but please let me know if you have any specific issues with how to implement a request in GraphQL and we can take another look.

@m1l0sz
Copy link

m1l0sz commented Dec 17, 2024

this is just a deprecation, they are not actually removing the endpoints. the tap will continue to work (such as it does) afaik.

@glevineLeap
Copy link
Author

@m1l0sz Deprecation already occurred as of 2024-04. The migration off these endpoints is a hard requirement as of February 2025, which I take to mean they will be disabling them:

REST Admin API /products and /variants endpoints on any version:

  • Public apps must migrate to supported GraphQL APIs by February 2025
  • Custom apps must migrate if they're integrated with stores that plan to have products with more than 100 variants. The REST API won't return more than 100 variants for each product and won't write to products with more than 100 variants.

https://shopify.dev/docs/apps/build/graphql/migrate/new-product-model#whats-changing

@m1l0sz
Copy link

m1l0sz commented Dec 17, 2024

they are not disabling them. if you read the thing you pasted, it does not anywhere say that they are being disabled. they will continue to work as they did before.

@gus
Copy link

gus commented Dec 17, 2024

they are not disabling them. if you read the thing you pasted, it does not anywhere say that they are being disabled. they will continue to work as they did before.

Is there a plan for migrating to non-legacy API endpoints? At some point, Shopify will indeed stop honoring these endpoints; they are deprecating them now, which implies they will no longer be supported.

@m1l0sz
Copy link

m1l0sz commented Dec 18, 2024

i personally think this is unlikely in the short to medium term.

this project does not appear to be actively maintained. though you could try fixing it yourself and submitting a pr.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants