Import SKU Mappings from CSV
POST/api/customers/:customer_id/sku-mappings/import
Bulk-import SKU mappings for a customer from a CSV file. The CSV must have a header row with columns customer_sku and product_id. Existing mappings for the same customer_sku are updated (upsert behaviour).
customers:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
CSV columns: customer_sku plus product_sku (or internal_sku). product_id is used only when a row has no SKU, and a SKU takes precedence over product_id. A row whose SKU matches no product is skipped. The file written by the SKU mappings export can be edited and imported again.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
Successful response
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.