v50

latestOpenAPI 3.0.0raw.githubusercontent.com2026-05-29208421.4 MB

Multi-language specification

Create or update specification translation

Inserts or updates language-specific information for a specification by its ID.

ℹ️ Learn more in the Catalog multi-language integration guide.

Permissions

Any user or application key must have at least one of the appropriate License Manager resources to be able to successfully run this request. Otherwise they will receive a status code 403 error. These are the applicable resources for this endpoint:

Product	Category	Resource
Catalog	Content	Categories Management

put/api/catalog/pvt/specification/{specificationId}/language

Path parameters

specificationIdinteger required

Example:7

Unique identifier of the specification.

Headers

Content-Typestring required

Type of the content being sent.

Acceptstring required

HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.

Request body

Localestring required

The locale code for this translation. It follows the IETF BCP 47 standard, such as 'en-US' for English (United States), 'en-ES' for Spanish (Spain), or 'pt-BR' for Portuguese (Brazil).

Namestring required

Translated name of the specification.

Descriptionstring nullable

Translated description of the specification, limited to 15 characters. When updating, if the field is not provided, it will turn to null.

Response

Created