Get Raw Order Data
GET/api/shipfusion/integration-instances/:integration_instance/orders/:order/raw
Fetch the raw, un-persisted Shipfusion shipment JSON for a single order, live from the Shipfusion API. Mirrors the Shopify order detail "Load Raw Data" panel — it powers the ShipFusion order detail page's expandable "Raw Data" JSON tree viewer. Unlike sync-detail, this NEVER writes to the local row; it is a read-only transparency/debugging fetch.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
ShipFusion exposes a single REST API (no GraphQL), so there is one source — no REST/GraphQL tabs.
The :order path variable is the SKU primary key (route-model binding). No request body, no query params.
Responses:
• 200 { data: <raw shipment JSON object> } — the complete shipment payload straight from Shipfusion.
• 200 { data: null, unavailable_reason: string } — Shipfusion answered HTTP 200 but with responseStatus: "error" or a non-empty errors array (e.g. the order was just submitted and the warehouse has not populated shipment detail yet). The frontend shows the unavailable_reason message with a Retry button.
• 404 { error } — the order does not belong to the given integration instance.
• 500 { error, message } — the live fetch to Shipfusion failed (network/timeout/upstream error).
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 429
- 500
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not Found
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.
Internal Server Error