I’m trying to test this URL using the new FulfilmentOrder REST API:
https://{SHOP}.myshopify.com/admin/api/2023-01/fulfillment_orders.json?status=open&financial_status=paid
but i get this error: “errors”: “Not Found” - real indication as to what is not found.
Can someone guide to me as to the correct URL needed to use the new FulfilmentOrder REST API to get a list of open orders that are marked as paid?
Start simple when trying to troubleshoot. What is the response you get back when doing a GET to the endpoint without the additional parameters (so not querystring).
@Jason is on point - if you’re troubleshooting, this is always a good way to start! To clarify completely though, if we look at the fulfillment order endpoint here in our REST docs, there is not a financial_status field attached to the resource. This is likely what’s causing the error here specifically.
Hope this helps a little bit - feel free to reach out again if we can assist with unblocking, etc.
I’d be careful about treating the REST, GraphQL migration as a simple endpoint swap. The biggest difference is usually the data model and query structure, not the authentication itself. In most migrations, the safest approach is to map the exact REST responses your app depends on, then rebuild those pieces as targeted GraphQL queries instead of trying to mirror every REST call one-for-one.
What has worked well for us is migrating feature by feature, adding logging, and comparing outputs during the transition. That makes it much easier to catch missing fields, pagination differences, and rate-limit behavior before switching fully to GraphQL.
If you’re also thinking about the business side of the migration, SEO impact, performance, and storefront growth during platform changes, RazorGrowth is a good example of the kind of growth-focused approach that looks at technical changes and conversion outcomes together.