Chris_Saunders
Shopify Staff
Contact Me
Status
Offline
Last Activity
‎01-16-2019 07:20 AM
Topic Started
0
Topics Started
Topic Solutions
0
Solutions
Post Count
591
Posts
Post Kudos
53
Likes

Community Badges

Hello Everyone, Our current implementation of signing OAuth requests is going to be getting changed. Instead of using the MD5 scheme, we are going to be including an HMACSHA256. You should start u...
There was a discrepancy in the naming of the variables sent in the tracking_numbers requests sent by Shopify. Previously the data being sent was order_ids though the values being sent weren't th...
We are making a change to the customers order listing API which may result in changes to your application. If you are using the /admin/orders?customer_id=[customer_id] endpoint to retrieve ...
Hello Everyone, A patch has been deployed that exposes the key that is used to sign webhooks that were created from within the Notifications area of the admin. If you have at least one webhook ...
Due to the reality that an order having a single transaction for payment is no longer always true (point of sale, gift-cards, etc.) we are going to be deprecating the gateway and payment_de...
There was an issue that was brought up with how the Shopify App gem was working where people couldn't use it along with Rails 4.1.x applications. It turned out that there was some naughty business go...
There was a bug in the system that allowed Basic-Auth API requests for private apps to sneak through even though the User did not match the API clients api key but they were using the correct access ...
All orders contain a payment field that can be accessed via liquid such as in an order confirmation email. Because orders support multiple payments, we recommend replacing any instances of {{ or...
Hello Everyone, About a month ago I kinda came to the realization that sometimes there's times you need to work with other aspects of the product that aren't really something you care about too much...
This is just a notice that the Fulfillments API is getting a minor change in how it works. tracking_number and tracking_url are going to be removed from the API with a preference for tracking_numbers...
We just released a feature for those who are subscribed to Categories or Topics. Now when a notification is sent out, we'll include a little snippet of the message so you can get some context. Longe...
No content to show

User Activity

It all depends on what was being sent. There's lots of additional data that is sent with a request (all a products variants, images, etc.) that can result in some pretty large API requests. It would all depend on how your clients or their customers a...
Some message bodies from Shopify can be upwards of a megabyte depending on the customer/order/etc. Can you configure Play to accept requests that large?
That's pretty odd. Is the content 331 spaces or something?
You can subscribe to the API Announcements section. Only Shopify employees can submit articles so you shouldn't need to worry about too much spam/unrelated content from that section.
Ryan,Currently webhooks created via the Admin cannot be signed because they don't have a secret. We've been talking about this internally and are looking into some ways to solve the solution. It'll most likely be a secret associated with a shop that ...
You mean find out the customers ID without having the customer submit a form or click a link to your shop with their ID in it?We cannot share anything from the Session with you because that is limited to the Shopify domain.
I'm sorry but I'm afraid that you'll need to perform an update on each metafield individually. While you do get metafields associated to an object you cannot update them.I'll admit that this is really odd considering you can attach metafields to a va...
Those values are somewhat variable and aren't guaranteed to be consistent depending on the CarrierService integrations the Shop may be using.Because of this I don't think we can a list of all the shipping types since it very much depends on the servi...
You need to migrate your data over in the manner that Michael talked about. The data being stored is the same but because you set it to integer it's getting coerced from a string of 9.5 to 9
The values are stored as strings because it's the "common denominator" of data-types. So we are just coercing the data to the expected data-type when we read it out of the database. So if it's an integer we coerce it into an int.
I've written up a little migration guide / explanation of whats going on and how to resolve it. I'd like to thank Michael Klett for his notes about the Shopify API gem since I used them as part of the guide.Thanks for all your feedback and apologies ...
You'll need to update your metafields such that they are stored as integers. So get all your metafields of interest and simply update their value_type.PUT /admin/metafields/1234.json { "metafield" : { "value_type": "string" } }This was broug...
Yeah, it's kind of one of my peeves with ActiveResource. It sends everything instead of just the data that changed Thanks for sharing!
This widget could not be displayed.
This widget could not be displayed.