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

[Shopify]: check if our integration is affected by shopify changes as of 1st April 2023 #4650

Closed
1 task done
ndeet opened this issue Feb 15, 2023 · 2 comments
Closed
1 task done
Labels

Comments

@ndeet
Copy link
Contributor

ndeet commented Feb 15, 2023

What is your BTCPay version?

v1.7.11.0

How did you deploy BTCPay Server?

docker

What happened?

Report by user using the Shopify integration. He got an email from shopify warning about changes in the REST API effective with 1st of April 2023.

One of our shopify integration users reported that the following fields will be removed, see original post here

Warning that april 1st certain API requests will be rejected:

The "total_price_usd" field in the "Order" section has been rejected by the ordering resource of the Admin REST API.

The "origin_location" and "destination_location" fields on items have been rejected by the ordering resource of the Admin REST API.

As part of inventory management at multiple locations, a change was introduced that caused a break for the Order.line_items.fulfillment_service field. This field should be removed from both the GraphQL and REST API for the admin area. When using the GraphQL API, consider using FulfillmentOrder.assigned_location. If using the REST API, see FulfillmentOrder.assigned_location for more information.

How did you encounter this bug?

Use shopify integration.

Relevant log output

No response

What browser do you use?

No response

Additional information

No response

Are you sure this is a bug report?

  • I confirm this is a bug report
@pavlenex
Copy link
Contributor

Probably a duplicate of #4510 but will leave this one opened as it has more context, this is certainly something we should prioritize.

@ndeet
Copy link
Contributor Author

ndeet commented Feb 16, 2023

Oh my bad, did not search. I think we can close this one then, I added the link to the changelog on the original issue.

@ndeet ndeet closed this as completed Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants