Common Failure Reason for Swagger Files Upload

You may see the following “Response Code” after uploading a swagger file, please refer to “Remarks” to see what you can do to proceed.

Response Code	Message	Remarks
102	Processing	The swagger file is under processing, you may check again for updates in a few minutes
200	Upload Success
202	Accepted
400	Invalid Swagger/OpenAPI file	Check 1) Swagger/OpenAPI file not in json or yaml format and extension 2) Invalid Swagger/OpenAPI file against the Swagger 2.0 schema (opens new window) or OpenAPI 3.0 Schema (opens new window)
500	API Connection Error	The Swagger file may have some syntax error. You may use a tool like openapi-lint (opens new window) or manually identify syntax errors. Please refer to Debugging Error 500 on Swagger Upload for more details.
590	Unsupported protocol	Check if protocol is http or https
591	Path "${path}" contain invalid character	Check if invalid characters exist in path - query param should not be included in the endpoint
592	No server is provided in OpenAPI file	Check if server/host specified in file. OpenAPI Spec should has at least 1 server for OAH construction
593	Variable substitution in server URL is not supported	Check if substitution (e.g ${name[selector]}) exist in server URL
594	Server hostname "${apiHostname}" belongs to gateway	Check if hostname same as OAH gateway
595	Server hostname "${apiHostname}" is private	Check if hostname is in private networks e.g ip is local loopback or single class A private network or 16 contiguous class B private networks or 256 contiguous class C private networks