Hey Team,
I am trying to integrate our IdentityNow v3 API with one of our partners. I am utilizing the OpenAPI 3.0 Spec that is available to download from developer.sailpoint.com. While performing an online validation on the swagger file, the validator throws some errors. I have tried it with only - https://editor.swagger.io/
Can anyone confirm if the IdentityNow Open API 3 spec is valid?
Also is there a swagger 2.0 spec available for our IdentityNow v3 API’s?
Hello Prashant,
The api spec from developer.sailpoint.com is valid, with that being said there are a few references that do not resolve correctly which are the errors you are seeing. We are working to correct these in the upcoming releases of the specification.
We do not currently have a swagger 2.0 specification available.
@prashant_kagwad to elaborate on @tyler_mairose’s answer, we do not keep our API specs in a single flat file. We make use of $ref in OpenAPI to break out our OpenAPI specifications into multiple files.
It is because of this use of $ref that you are not seeing the validation from swagger. Our API spec, though, is indeed valid.
Thank you for validating that. Any timelines on when that might be available?
I am using third party converters to convert the Open API 3 spec to swagger 2.0 as some platforms are not yet updated. It might be better to have that on the forum as well.
That makes sense but due to imports and other validations on third party platforms it might be better to have them in a single file that way these errors dont show up.
This will however become a major issue for platforms that may not perform the reference resolution or have swagger 2.0 support. Just a suggestion.
I don’t know that having one file with that many lines is practical, but we will be open-sourcing the entire spec soon, including all the reference files, which will solve your problem 
As for Swagger 2.0 support, we don’t plan to regress from OpenAPI 3.0 so you may have to consider different options for anything that requires Swagger 2.0 or older.
Any ideas when this might happen?
No timelines in place yet. I will let you know once we do have one.