Submit Fulfillment to Temu
POST/api/temu/:integrationInstance/fulfill
Registered by the shared salesChannel route macro (POST /api/temu/{integrationInstance}/fulfill). Submits an existing SalesOrderFulfillment to Temu. Temu does NOT auto-generate tracking — a carrier tracking number must already be stored on the fulfillment OR be supplied here in the request body (it will be persisted).
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Validation:
- sales_order_fulfillment_id (required, integer, must exist in sales_order_fulfillments)
- tracking_number (nullable, string, max 255)
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.