Bulk Create SKU Products
POST/api/temu/:integrationInstance/products/create-sku-products
Creates internal SKU products from Temu listings and links them, running as a queued background job. If a listing's candidate SKU already exists internally, the listing is linked to the existing product instead of creating a duplicate. Field mappings configured for the instance control how listing fields populate the new products.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Request body:
create_all_products(boolean, required) — whentrue, processes every listing for the instance.ids(array of integers) — specific Temu product ids; required whencreate_all_productsisfalseand nofiltersare supplied.filters(string, optional) — serialized filter expression, resolved to a set of ids before the job is dispatched.mappings(array, optional) — field mappings to persist before creation; each entry haslisting_field(string),sku_field(string) andparsers(array of{rule, args}transforms).initial_mapping(boolean, defaultfalse).
The response returns immediately with a tracked_job_log_id that can be used to follow the job's progress.
Authentication: Requires Bearer token.
Bulk selection contract:
- {"create_all_products": false, "ids": [1, 2]} — create for the given channel product IDs
- {"create_all_products": true} — create for all unmapped products on the integration instance
- {"create_all_products": true, "filters": {...}} — create only for products matching the filters. The filters object accepts the same filter keys as the corresponding products list endpoint (bare column keys) and/or a "filter_groups" tree (base64-encoded JSON). When filters match no products, nothing is created and the response message is "No products to create".
- create_all_products is required; ids is required when create_all_products is false and no filters are sent.
- Legacy {"conjunction", "filterSet"} filter payloads are rejected with 422.
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.