Access to Api2 schema

[Ealfardan]

Hi @lubos,

I’m working on upgrading all my connections from Api to Api2 and I was faced again with this issue

@Ealfardan

was planning to release a full connector function with dynamic routes, however, I’m facing an authorization issue with Power Query, since logging in to “/api2” requires basic credentials, while accessing anything beyond that requires the x-api-key.

Power Query cannot handle that gracefully and it will cause it to prompt the user to set credentials to anonymous everytime the route changes. This results in an annoying user experience, so I would leave the full connector until I can sort this issue.

My solution was to copy the entire schema text and embed it inside my connections. I assume that Api2 being Open Api shouldn’t see frequent changes such that it becomes a chore to update the schema – but it would still be a relief to hear that from you.

Also, are there any plans to either:

1. make an updated schema publicly accessible, or

2. create a path for the schema within Api2 so it’s retrieved using the Api key?

[lubos]

@Ealfardan

make an updated schema publicly accessible, or

The schema is publicly accessible via https://manager.readme.io/reference but eventually I’ll make that page be shown within Manager itself so it doesn’t depend on 3rd-party URL.

@Ealfardan

create a path for the schema within Api2 so it’s retrieved using the Api key?

It can be accessed without api key. There are no secrets in it. When you navigate to ~/api2, you will get schema in JSON format.

[Ealfardan]

@lubos

The schema is publicly accessible via https://manager.readme.io/reference but eventually I’ll make that page be shown within Manager itself so it doesn’t depend on 3rd-party URL.

That should do just fine