I see a post about 2022-04 deprecation being postponed until June 30th. However, we are still using 2020-04. It's basically the same logic. Is only the 2022-04 version being postponed?

I received this answer already. The answer was no. It's not available via Rest Admin API. It seems like they are moving away from Rest in favor of GraphQL since GraphQL is less taxing on their systems.

I'll try to keep this simple. Here is what I have done to achieve a process very similar to the soon to be deprecated procedure. I'm going to make a couple of assumptions. Based on the old logic, you probably already have a way to figure out the orde...

Remove the line of... number: "12312312", from your example above. I was able to get both to go on the order. 

It says in this article it supports all and more than the deprecated API. Can you show the JSON Body needed with 2023-01/fulfillments.json to populate tracking_numbers and tracking_urls with more than one number and more than one url? Our customers o...

Trying to convert from the deprecated way of adding tracking numbers to an order. So fulfillments REST API here we go. I can successfully make a fulfillment with single tracking number / url. When reviewing the response, there is tracking_number and ...

I also have the same problem. Our company sells large product that ships in multiple boxes to meet the requirements of UPS/FedEx shipping limitations. Have you found a solution?