Enhancement to the FME Server REST API

The REST v3 API is deprecated as of 2025.1 and replaced with v4, where you have a new endpoint /jobs. The endpoint /transformations/jobs does not exist anymore.

The /jobs endpoint has improved filtering possibilities, although not quite what you are requesting. But you for your use case you could do something like this:

 /fmeapiv4/jobs?status=success&sort=timeStarted_desc&limit=50&offset=0

This will return the last 50 successful jobs, sorted descending by the start time. If you can remember the job ID between requests, it should be fairly easy to avoid processing/reporting the same jobs multiple times.

​@david_r  Thank you for looking into this!

To provide some background: we have a workspace scheduled to run every minute on our FME Flow, and it's critical for us to ensure that it executes reliably on this schedule.

To monitor this, we plan to implement a feature in our monitoring system that runs every 10 minutes. This feature allows us to configure an HTTP URL—along with the expected response pattern in regular expression format. The monitoring system will send an HTTP request to retrieve details of the most recent successful job executions within the past 3 minutes. If the expected job records are found using a regular expression match, the system will consider it healthy. Otherwise, it will trigger alerts to notify us of potential issues. However, from what I understand, the current v3/v4 API may not provide the necessary endpoints or data for this monitoring approach.

I do a lot of monitoring on different systems, but I usually do it the other way around. Critical workspaces are implemented as Automations with the success and failure ports connected to webhooks (or similar) that logs the result directly. If we expect a particular cadence for the log entries, I also monitor the log for any missing entries, as there should be at least one success or failure entry per scheduled time slot.