FME Server has a good range of Rest api calls but they aren't all documented. For instance, named connections are avaliable by fmerest/v3/namedconnections/webservices, version control push by
/fmerest/v3/versioncontrol/remote/push. It would be great if more of these calls could be documented
yes please - this would be particularly useful for supporting customers
Understanding that some API calls are undocumented for the reason that they are liable to change in subsequent releases, perhaps those "unstable" calls could be hidden by default and only exposed with explicit selection of a checkbox similar to the "Hide Advanced Calls" checkbox on the current API documentation. Maybe something like "Show Beta Functionality", with appropriate warnings beside each such call in the documentation.
Noting Ideas created for specific endpoint exposure here as well:
Automations Components: https://knowledge.safe.com/idea/111914/publish-fme-server-rest-api-endpoints-for-retrieva.html?
Named Connections: https://knowledge.safe.com/content/idea/43115/named-connections-editing-via-api.html
Version Control: https://knowledge.safe.com/content/idea/75121/expose-versioning-through-the-fme-server-rest-api.html
Thank you to everyone who has voted and commented on this! We have marked this idea as 'Under Consideration' because we have started work on the next iteration–Version 4–of the FME Server REST API.
Currently, we plan to have V4 as "Technical Preview" for 2021 and we expect that it will be a full release cycle until it takes place of the V3 REST API (i.e. FME Server 2022). Expect more details to come (e.g. migration guide) as development progresses.
We have made note of the requests in this idea description and those in the comments. Any major updates or decisions related to those requests will be posted here.
Hi @rylanatsafe, any news on the availability of v4 and the API for named connections in particular? Ideally, we would like to leverage the API to create and maintain database connections in an automated manner. Use case: update database connections programmatically to point at different staging or test servers. This includes modifying the password.
@david_r the V4 API endpoints for web and database connection management will be in progress soon.
Updating parameters, such as the db connection password, should be in scope for this work.