Forum Discussion

gh0stwr1ter's avatar
gh0stwr1ter
New Contributor
3 years ago

Error while importing openapi .json file

I am new to ReadyAPI, however, I am unable to get any of my openapi .json (3.0.0) files to import successfully.  I have attached a sample .json file I am trying to import as well as a screen shot of ...
  • joejoyce's avatar
    joejoyce
    3 years ago

    I'm not sure what the granular differences are between Postman's import mechanism and our import mechanism, but I can say that a completely valid and resolved API definition file ideally shouldn't have any references to inaccessible external components. You could consider them like external dependencies that the file doesn't have access to, which could potentially cause issues depending on the use case for the API definition. I think reaching out to the API provider would be a good step, as they could have a separate file where these components are stored, or potentially a fully-resolved version of the API definition file that contains the referenced components. Let me know how that goes! I hope this helps. 

joejoyce's avatar
joejoyce
Staff
3 years ago

Hey gh0stwr1ter. ReadyAPI is rejecting the definition file because it isn't a completely valid OpenAPI file, due to the missing components that are being referenced in the error message, e.g. "create_alert_policy_input" and "get_alert_policy_resp". I'm pretty sure that once you find  those components and add them to the file, the import will be successful. Could they be stored in some other location, locally or in the cloud?