What happened to the “includeAutomations” parameter in the “schedules” endpoint in the REST API? We were using that to pull all Flow scheduled Workspaces and Automations for a report. Has it been replaced with something else?
Solved
REST API "includeAutomation" Parameter on "schedules" Endpoint
+11- Contributor
Best answer by pmcpherson
Answered my own question. There is an (apparently) undocumented parameter in the V4 schedules endpoint, called sourceType. It appears that “automation” and “all” are valid values. Maybe there are others? The following worked for me, and basically matched the V3 results, except some of the returned values are different. I reworked the downstream part of the workspace to accommodate the changes. Seems to work fine now. Here is the correct endpoint format.
GET
$(FME_SERVER_WEB_URL)/fmeapiv4/schedules?limit=1000&offset=0&sourceType=all
+11- Contributor
- Best Answer
Answered my own question. There is an (apparently) undocumented parameter in the V4 schedules endpoint, called sourceType. It appears that “automation” and “all” are valid values. Maybe there are others? The following worked for me, and basically matched the V3 results, except some of the returned values are different. I reworked the downstream part of the workspace to accommodate the changes. Seems to work fine now. Here is the correct endpoint format.
GET
$(FME_SERVER_WEB_URL)/fmeapiv4/schedules?limit=1000&offset=0&sourceType=all