@rit001 Sorry, I guess I’m misunderstanding what you’re after here. Your original post in this thread was asking if we had an OpenAPI file available. You then followed up asking if there was an update, to which I sent you a link to an OpenAPI spec file you could potentially use with swagger.io.
What you’re talking about in your last response seems to be a separate issue? Are you seeing discrepancies with how the API is documented and how it actually works in practice somewhere? The points you mention seem more to be functionality/feature gaps in the API, which shouldn’t prevent you from using the OAS spec file for the API endpoints we have available now.
As far as your individual examples:
- Regarding the service token lookups – could you elaborate on what you’re typically trying to do here? Is the scenario usually something along the lines of the token having been revoked in some environment and you’re having to determine what project+config it was for so you can create a replacement? This seems to be what you’re discussing here.
- When it comes to IP access control APIs, that’s just something we haven’t implemented yet. Unfortunately, this isn’t a widely used feature and we get very few requests around it, so adding support for it in the API hasn’t been a priority. Eventually, we do want to have full API coverage though.
Regards,
-Joel
