Skip to main content
Question

404 Response for Swagger APIs defined in Swagger Spec

  • February 22, 2019
  • 1 reply
  • 71 views

When I call

/fmerest/apidoc/v3/spec/

Some of the APIs listed in the response such as:

{"path":"/management","description":"FME Server Management"}

Return a 404 when queried like:

curl -X GET \
  http://localhost:8080/fmerest/apidoc/v3/spec/management \
  -H 'Authorization: fmetoken token=theTokenGoesHere' \
  -H 'Content-Type: application/json' \
  -H 'Postman-Token: 631c22d9-2a5e-4273-8bf1-2090800df932' \
  -H 'cache-control: no-cache'

I'm trying to create an api client using swagger-codegen and I think this issue is causing swagger-codegen to fail.

 

 

 

I haven't gone through all the spec listed endpoints but tempstore is another one that returns 404.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

nathanatsafe
Safer
Forum|alt.badge.img+9

Hi @rcollette,

 

 

Thanks for your question. Can I ask what version of FME Server you're working with? I'm thinking that some of these endpoints may just not be exposed for use via the API (ie internal use only), but I can look into this with the FME Server team.

 

Thanks,

 

Nathan