This requires two calls - the first to build the XLIFF and the second to obtain the XLIFF data from the server for storage client-side.

1. Building the XLIFF

URL: /segments/remote_build_xliff
Post Data: session_id, target_id

session_id

The unique key returned in the initial login call.

target_id

The value of target_lang_id obtained when the PDF was uploaded.

Returns

On success, a JSON structure containing progress information. Any errors related to credit usage will be reported via the progress monitoring mechanism. See Progress Messages.
On failure the HTTP status code will be set to something other than 200.

The JSON structure will contain amongst other things, the following fields:

task_id

The unique id of the task which corresponds to a separate thread on the server. Use this id to obtain status information about the task via the remote_task_status call.

Notes

The XLIFF contains a unique ID linking it to the PDF/language combination from which it came. This ID must be retained in any XLIFF later uploaded so the system can direct it towards the correct PDF.

2. Getting the XLIFF Data

URL: /segments/remote_download_xliff2
Post Data: session_id, target_id

session_id

The unique key returned in the initial login call.

target_id

The value of target_lang_id obtained when the PDF was uploaded.

Returns

The name of the XLIFF file just downloaded is encoded into the HTTP header. The rest of the content is the XLIFF data itself.