Export in one api call
It would be much easier to script the translation export if the export api directly responded with the translation requested rather than a url. I'd love to be able to make a single api call with curl to specify the file and language, and not have to mess with parsing the response.

-
Phil commented
"Simple" would be a static three line shell script to sync english up and two translations down. The two-request download api forces us to write a program to make request 1, parse the response, and generate request 2. A program that will need to be maintained that is there purely to support a tool we are paying for.
-
Unfortunately no. Either make two requests or parse the terms_list and build your own file. Making two requests suddenly seems simple :D
-
Phil commented
Thanks for the quick response. Is there a way to get the output of the terms list api to match what's returned in the export? The example response isn't suitable for our translation libraries. The response from the export is what I'm after, just in one api call, such as with the terms list api. The current export api requires me to parse the response from the first request in order to get the url for the second request. This makes scripting vastly more complicated.
Thanks
Phil -
Hello,
You can use the list method from terms: https://poeditor.com/docs/api#terms_list with the optional language parameter set to get the translations in one request. The format of the response is JSON.