If the API changes in an incompatible manner this is listed explicitly in the "important release notes" section of each releases changelog.
Enables the usage of third party TM and MT systems in translate5. To support a MT / TM ti must be implement as a service in translate5. This is quite easy and usually a matter of days. Please contact us, if you need help on this.
|entityVersion||integer||GET only, set by server|
|langResUuid||string||GET only, is ignored on PUT/POST, is an auto generated UUID set on language resource creation. Contains a unique identified for the language resource.|
Custom name of the match resource.
|sourceLang||integer||GET / POST, non editable after creation; numeric DB id of the language|
|targetLang||integer||GET / POST, non editable after creation; numeric DB id of the language|
Custom color of the match resource in hexadecimal form, used in the GUI.
POST / GET, non editable after creation
POST / GET, only, set by setting a resourceId
GET only, set by setting a resourceId
POST / GET, can not be changed
|filebased||boolean||GET only, set by setting a resourceId|
|searchable||boolean||GET only, set by setting a resourceId|
|customerIds||array of integers|
POST, PUT: contains an array with customerIds to be assigned to that language resource
|customerUseAsDefaultIds||array of integers|
POST, PUT: contains a subset of customerIds of the above customerIds. The here referenced customers use this language resource by default to read from.
|customerWriteAsDefaultIds||array of integers|
POST, PUT: contains a subset of customer ids of the above customerUseAsDefaultIds. The here referenced customers use this language resource by default to write into it.To be able to write by default
the customer must be also set as read as default.
Configuration of the Language Resources