Preview Fulfillment Preflight
POST/api/temu/:integrationInstance/fulfillments/preflight-preview
Runs the same Temu shipment-confirmation checks as the stored-fulfillment preflight, but against raw input values instead of a persisted fulfillment. Use this to validate a fulfillment while it is still being composed, before anything is saved.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Request body (all fields optional — omitted values are reported as blockers):
warehouse_id(integer) — local warehouse id; must be mapped to a Temu warehouse.shipping_method_id(integer) — local shipping method id; must be mapped to a Temu carrier.tracking_number(string, max 255) — carrier-issued tracking number.
The response shape matches the stored-fulfillment preflight: can_submit, blockers (each with field, message, fix_path), and resolved (carrier_id, warehouse_id, tracking_number).
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 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 — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.