Deckard

I apologize for the distractions here. I really feel like a dummy. I started with the Swagger Codegen tool and it refused to ingest that JSON file complaining that it was malformed for an API spec. However, NSwag Studio will ingest it just fine. Scratching my head. Thanks for your patience.

Hi Carlo, Thanks very much for your response. I'm afraid that I have caused some confusion here by not being very clear on what I'm after. I apologize. When I say "spec" I am referring to the Swagger specification file that defines the API, and is subsequently used as to generate the documentation, the server stubs, and client bindings. This is a YAML file or can also be interchanged as JSON. It is this file, literally the specification of the API, in which I'm interested. It was formerly called the Swagger Specification but is now called the OpenAPI Specification.

Thanks, tinkergnome. I'm not after the human readable doc, I'm after the JSON file that defines the API so I can generate a client with my chosen language bindings. Is that served up somewhere in the printer perhaps? If so, I haven't been able to find it.

Hi, I’m new here and I, too, would like to generate a client. Can someone point me to a spec that I can use as an input to the Swagger tools? I’ll even take the buggy one for now. Thanks, Deckard