...
Proposals export for a TermCollection, as XLSX | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Request | GET editor/languageresourceinstance/export | ||||||||||||||||||
| Params | collectionId Required. Id of a TermCollection to be exported. | ||||||||||||||||||
| exportDate Optional.If given, should be a date in YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS) format, so that only proposals happened after that date will be exported. | |||||||||||||||||||
Important: response for this endpoint comes with 'Content-Disposition: attachment' HTTP header to provide a direct download of an exported file.
Important: If no proposals found, then the endpoint will respond with the following XML text
| |||||||||||||||||||
Check if given terms exist in any of accessible TermCollections | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Request | GET editor/termcollection/searchtermexists | |||||||||
| Params | searchTerms Required. Should be given as JSON-encoded array structured in the following way: | |||||||||
| targetLang Required. Should be given as rfc5646 language code representing a major language (e.g. 'en') or with sublanguage (e.g. 'en-US'), but keep in mind that sublanguage will be ignored. | ||||||||||
Important: response for this endpoint comes with 'Content-Disposition: attachment' HTTP header to provide a direct download of an exported file.
| ||||||||||