Refresh Orders
POST/api/temu/:integrationInstance/orders/refresh
Queues a background job that pulls the latest orders from Temu and upserts them into the local order list. The job runs on a serialized queue so overlapping refreshes for the same instance cannot race. The sync window starts just after the most recent stored order (or the instance's configured start date when no orders exist yet).
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
After orders are saved, linked sales orders for the fetched page are also brought up to date. The response returns immediately; there is no job id to poll on this endpoint.
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.