Get Fulfillment Preflight Result
GET/api/temu/:integrationInstance/fulfillments/:fulfillment/preflight
Validates a stored fulfillment against Temu's shipment-confirmation requirements before submission. Temu requires three values per package — a mapped carrier, a mapped warehouse, and a tracking number — all of which must be configured on the platform side. This endpoint reports exactly which requirements are unmet so submission failures can be prevented up front.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Response fields:
can_submit(boolean) —truewhen every requirement is satisfied.blockers(array) — one entry per unmet requirement:field(carrier,warehouseortracking_number), a human-readablemessage, andfix_path(a relative in-app settings path where the mapping can be corrected, ornullwhen the fix is on the fulfillment itself).resolved(object) — the values that would be sent to Temu:carrier_id(Temu logistics provider id),warehouse_id(Temu warehouse id string),tracking_number. Unresolvable values arenull.
Returns 404 when the fulfillment does not belong to this integration instance.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 429
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.