Forum Discussion

jcsreddy's avatar
jcsreddy
Occasional Contributor
7 years ago

Getting -> swagger compliance testing failed. invalid content type: application/json; charset=UTF-8

Team,   I am using Ready API 1.8.5, and in that I am using 'Swagger Compliance Assertion' for validating the response to check if it is adhering to Swagger 2.0 [OpenAPI 2.0] or not.   While doing...
JHunt's avatar
JHunt
Community Hero
7 years ago

In a sense, an OpenAPI specification is comparable to a WSDL - it is a machine-readable file that describes how an API will behave. This assertion is about checking that your API behaves as described by its OpenAPI specification, not about whether it complies with OpenAPI as a standard (whatever that would mean).

 

It sounds like your API returned a response with a Content-Type header of "application/json; charset=UTF-8", but that was not what was described among the possible response Content-Types in the spec.

 

If you still think the assertion should pass, you will need to give the spec and the response. And probably ask it on the SoapUI Pro forum (us Open Source users have very limited features for Swagger/OpenAPI).

  • jcsreddy's avatar
    jcsreddy
    Occasional Contributor
    7 years ago

    Hi,

     

    Thanks for your response.

    I am attaching the request and response, and my objective is to ensure that 'Swagger Compliance Assertion' is passed.

     

    Thanks,

    Chandra.

Related Content