Merge Product Type
POST/api/v2/product-types/:type/merge
Move every product (archived products included) and every per-channel category-map row from this type onto another leaf type, then archive this one. Both types must be leaves and the target must be active. Where the target already has a map row on a channel, the target's row is kept and this type's row is dropped; those channels are listed in meta.conflicting_channel_ids so their mappings can be checked. Responds with the target type.
products:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Fields:
into(required, integer) — the active leaf type to merge into.
Response meta: moved_products, moved_map_rows, conflicting_channel_ids (sales channel ids whose existing mapping on the target won).
Requires permission: product_types.update
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.
Unprocessable Entity
Response Headers
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.