Fulfillment creation/404 error occurs

Retired Boards Appdev Fulfillment Api

Topic summary

Problem: Creating a fulfillment via the Fulfillment API returns a 404 (Not Found) error.

Request details:

  • Endpoint shown as /admin/api/2023-01/fulfillments.json (link points to 2022-10).
  • Method: POST.
  • Payload includes line_items_by_fulfillment_order (written as “line_items_ by_fulfillment_order” in the post), tracking_info (company, number, url), notify_customer, and location_id. Values are shown as placeholders.

Recent updates:

  • Support requested the X-request-id to review logs.
  • Reporter provided X-request-id: 23e1d24b-e076-4951-8e38-3766fb920593.
  • Another participant asked if it was resolved; the reporter said they tried but didn’t get much information.

Context/notes:

  • 404 indicates the resource or route wasn’t found; could relate to endpoint, resource IDs, or permissions (not analyzed in thread).
  • X-request-id is a unique identifier used by support to trace specific API calls in logs.

Status/outcome:

  • No resolution yet. Awaiting support log review using the provided X-request-id. Open questions remain on the exact cause of the 404.
Summarized with AI on January 23. AI used: gpt-5.
1

Dear Shopify Support Team,

The issue I am experiencing is that whenever I attempt to create a fulfillment for an order, I receive a “404 error” message.

POST to API (or use your method of choice)

API: https://xxx.myshopify.com/admin/api/2023-01/fulfillments.json

JSON:

{
“fulfillment”: {
“line_items_by_fulfillment_order”: [{
“fulfillment_order_id”: {api.fulfillment_orders id},
“fulfillment_order_line_items”: [{Line Items Fulfillment Array}]
}],
“tracking_info”: {
“company”: “{Fulfillments: Tracking Company}”,
“number”: {Fulfillments: Tracking Number},
“url”: “{Tracking URL}”
},
“notify_customer”: false,
“location_id”: {fulfillment_orders assigned_location_id}
}
}

2

Hi there :waving_hand:

Could you provide the X-request-id of a failing request, so that I can review the logs?

3

Hi Liz, below is the X-request-id of my failing API call.

23e1d24b-e076-4951-8e38-3766fb920593

4

Have you already dealt with it on your end?

5

yeah I try it but do not get much information