Hi,
For the Export endpoints (see jobs export and queue export) both in the end return a .zip .csv file.
This has a couple of things that could be nicer for programmatic access:
- .zip with a single file adds a bit of a headache. Since it’s a single file, .gzip would be much better.
- Having the exported data in .csv is very brittle, especially for queue items - the exception reason often has line breaks (due to a pretty common practice of doing a
exception.ToString()on appex).
Now for the request → it would be great if there would be export endpoints (or options on existing ones) that would produce a .json.gzip version of the export. That way getting the data out programmatically would be much more streamlined.
In today’s day and age, the .json output would be useful for end users as well, since importing it to Excel is trivial and it solves the line break issue that standard .csv exports have.
PS. I know that in .net world handling a .zip or a .csv with line breaks is not complicated. But, it adds extra steps/dependencies that wouldn’t really need to be there (and also not everything is in .net and/or has filesystem access 
). Even within .net, with .json.gzip it’s very easy to stream-unpack-deserialize in one go, making it the (imho) most streamlined way of handling when you need to transform/work on the data a bit more than just a pass through export.