...
Export TermCollection as TBX | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Request | GET editor/languageresourceinstance/tbxexport | |||||||||
Params | collectionId Required. Id of a TermCollection to be exported. | |||||||||
tbxBasicOnly=(0|1) Required. Whether to export only TBX Basic standard attributes + processStatus, rather than all attributes. | ||||||||||
exportImages=(0|tbx|zip) Required. Whether to export images:
| ||||||||||
Important: response for this endpoint comes with 'Content-Disposition: attachment' HTTP header to provide a direct download of an exported file.
|
Export TermCollection as XLSX | |
---|---|
Request | GET editor/languageresourceinstance/xlsxexport |
Params | collectionId Required. Id of a TermCollection to be exported. |
Important: |
XSLX export is a two-step operation consisting of prepare-step and download-step. Prepare-step may take a while depending on TermCollection size, and is implemented in a way that allows to track the preparation progress measured in percents of already exported term entries vs total term entries in that TermCollection, so progress is printed during the export.
Once export is Done, browser page is reloaded with javascript and the download is started - so yes - all this is intended to work via browser. Example 1: REST API request via curl-command Step 1: curl -c cookies.txt http://yourTranslate5app.com/editor/languageresourceinstance/xlsxexport?collectionId=XXX This is the first needed request, that starts and keeps session and shows the progress as pure HTML code during execution (see below)
- step 2: curl -c cookies.txt -o file.xlsx http://yourTranslate5app.com/editor/languageresourceinstance/xlsxexport?collectionId=XXX This is the second needed request that preserves the session and responses with 'Content-Disposition: attachment' |
header and raw file data as response body, which is saved into file.xlsx on your local computer from where you call the curl-command Example 2: REST API request via php curl - see both steps below |
|
|