As of FME Flow 2025.1, the V3 REST API has been deprecated. The current API will remain accessible, but no new features or general bug fixes will be implemented. Starting with FME Flow 2026.1, the V3 API will be removed. We encourage all users to prepare their systems for this change.
The V4 REST API offers enhanced security and usability, including new and reorganized endpoints, as well as the removal of certain endpoints. For information on migrating from V3 to V4, please see the FME Flow REST API V4 documentation and click on the heading Migrating from REST API V4.
Consideration
The FME Flow REST API V3 documentation includes a resultDatasetDownloadURL in the response for the endpoints below, which are used to submit jobs to FME Flow programmatically:
POST /transformations/submit/{repository}/{workspace}
POST /transformations/transact/{repository}/{workspace}
POST /transformations/transactdata/{repository}/{workspace}However, the resultDatasetDownloadURL is never included in the response.
Why This Happens
The resultDatasetDownloadURL is only included in the response when retrieving past jobs run against the Data Download service, for example, GET /transformations/jobs/completed. The response model for REST API V3 /transformation endpoints is shared, so the resultDatasetDownloadURL is included in the response documentation for other /transformations endpoints. This is a limitation of the REST API V3 documentation.
How to Resolve It
A Data Download URL can only be obtained by running a job through the Data Download service. Jobs can be run programmatically through the Data Download service using a workspace webhook, but not the REST API.
The tutorial Submitting a Job through an FME Flow Webhook URL provides an example using the Data Streaming service. The same approach can be used with the Data Download service.