downstream_appid:overcome-clothingstore.myshopify.com,curl_no:0,http_code:422,
url:https://overcome-clothingstore.myshopify.com/admin/api/2024-01/fulfillments.json,
total_spent_msecond_time:392,connect_spent_second_time:0.002952,dns_spent_second_time:3.2E-5,
start_time:2025-08-27 06:15:41.614,end_time:2025-08-27 06:15:42.006,
post_data:{"fulfillment":{"notify_customer":true,"tracking_info":{"company":"xxxx","url":"https:\/\/share.xxx.com\/?BR100250827061540627210010091275596&lang=pt_BR&sign=2a4472174c9ba086f9172b46fdffb2aa&source=shopify","number":"xxx"},"line_items_by_fulfillment_order":[{"fulfillment_order_id":xxx}]}},headers:["Content-Type: application\/json; charset=utf-8","X-Shopify-Access-Token: xxx"]
This is likely due to the API version being significantly out of date.
I would upgrade the API Version and ensure you requests match the expected payload as there may have been updates since 18 months ago.
Also I’d recommend looking at GraphQL for your endpoints as that is what Shopify is prioritising for development
2 Likes
Hey @Kyle_Zhou 
, I definitely agree with Jordan on this one, our recommendation would be to use the GraphQL admin API going forward:
We do also always recommend using the most up to date version of the API if possible (current newest version is 2025-07).
If you do need to use the REST API for legacy reasons though (like you’re maintaining an old integration for a merchant while waiting to update to GQL), we can still look into things if needed. If you’re seeing any further errors, feel free to share an x-request-id from the API response headers we send out and I’d be happy to take a look. Hope this helps!