Skip to main content
Manually trigger an export of results from a completed mapping job. Exports are generated asynchronously. When ready, you receive an exportFileId to download the file. If the job has no results or cannot be found, the response indicates failure without an HTTP error status.
Exports may also be triggered automatically depending on your organization’s export configuration. Use this endpoint when you need to re-export results on demand or generate an export outside the automatic schedule.

​
Request

​
string
required
UUID of the mapping job to export results for.
This endpoint takes no request body.

​
Response

This endpoint always returns HTTP 200 OK. Check the success field to determine whether the export was actually triggered.
​
boolean
required
true if the export was triggered successfully. false if the job was not found, had no results, or the export failed for another reason.
​
string
UUID of the generated export file. Present only when success is true. Use this ID to download the export file.
​
string
required
Human-readable description of the outcome. Provides detail when success is false.

​
Error responses

A 200 OK response does not guarantee the export succeeded. Always check success: true in the response body before using the exportFileId. If success is false, the message field explains why.

​
Example