I have been using a url like the one below to monitor my FME Server 2017. http://<server>/fmerest/engines.xml?token=<token> Since upgrading to FME Server 2020, this fails. Is there a similar API call I can make to get the same result?

Hi @bruce.tonkin​ ,

So we did retire the first version of our API in 2020. However, I believe this call in REST V3 should be similar: https://docs.safe.com/fmerest/v3/transformations/engines

To learn more go here https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html#!/transformations/list_get_2 It's the first call under Transformations

Let me know if that matches closely enough or if you need another call!

Thanks for the information. That did help me get one more step forward.

Using the new syntax with a new token, I now get a logon challenge in my browser. Would this mean the token is not valid?

http://<server>/fmerest/v3/transformations/engines?token=<token>

Oh try this instead and it should work!

http://<server>/fmerest/v3/transformations/engines?fmetoken=<token>

Thanks... works like a charm. Just the little things we get stuck on.