Olivier Mengué

In fact I just noticed that my account has plenty of completed “Batch Update Ticket” jobs, so I should be able to go forward with my implementation.

It would be helpful to have an API route that produce a job with 30 expected results, and every second one results is marked as completed until it is done.

That test route could also have parameters to produce failed results.

I'm writing a client that uses this API:

https://developer.zendesk.com/api-reference/ticketing/ticket-management/job_statuses/#list-job-statuses

I have no active jobs, so the current list of jobs is empty.

However I would like to validate my code that deserializes the list jobs when it isn't empty.

So how can I create fake jobs to check that my client works?

All the API routes that create jobs (by the way I haven't found a comprehensive list of those) are destructive, so I want to avoid destructing things for testing.

There is a "Bulk Import" feature to import users from a CSV file, but there is no corresponding "Bulk Export" as CSV. Only XML and JSON.

I wanted to tranfer users from one instance to another, so it looks like the only way is to write my own CSV exporter using the API. And the specification of the CSV import doesn't include the fields for all the data I can export. For example, I don't see how to include the timezone of the user in the CSV import.

The CSV format described here lacks much information available in ZenDesk. I would like to transfer some users from one ZenDesk instance to another. I had to build a custom CSV exporter using the API (because ZenDesk doesn't provide CSV export of users), but I don't know how to put the timezone in the CSV to import as this is not specified in the Bulk Import format.