List API Products associated to an API Proxy

Is there a way to get all API Products associated to an API Proxy?. Its just that I am getting an APIProduct mismatch in one of our APIs and I dont know what existing product it needs to be added to our App for me to be able to use it. I tried lookin gin the Edge APIs and I cant see it there. Its just that I want to know all of the products associated to an API Proxy so that when I open Edge UI, and look for a product that I found that is link to that API Proxy, I would then know the App where it is associated and check that app configuration among other things so that I could make it work on our own App with configurations copied from another App where that API is working. Atm I have to manually open all the Products in our organization to trace where this particular API proxy is configured, and it is time consuming and almost impossible to do given the hundreds of API Products and possibly dozens to hundreds more api proxy configured for an API Product.

 

Solved Solved
0 2 381
1 ACCEPTED SOLUTION

This works for Apigee Edge. 

https://github.com/DinoChiesa/apigee-edge-js-examples/blob/main/findApiProductForProxy.js

Does not work for Apigee X or hybrid with the "new Product configuration" option. 

If you use the -v option you should be able to see the Admin APIs this script invokes. 

And also, 

Be careful about "APIProduct mismatch".  It could be that the proxy itself is included in the API product, but not the PATH you're using.  If you specify paths other than '/**', then you need to consider that as well when diagnosing API Product authorization issues.

View solution in original post

2 REPLIES 2

This works for Apigee Edge. 

https://github.com/DinoChiesa/apigee-edge-js-examples/blob/main/findApiProductForProxy.js

Does not work for Apigee X or hybrid with the "new Product configuration" option. 

If you use the -v option you should be able to see the Admin APIs this script invokes. 

And also, 

Be careful about "APIProduct mismatch".  It could be that the proxy itself is included in the API product, but not the PATH you're using.  If you specify paths other than '/**', then you need to consider that as well when diagnosing API Product authorization issues.

Funny thing, I already have this repo from a previous question. My windows search must be trolling me, as querying product in it did not threw any existing scripts with name "product". Ahh, silly me, i should have just manually looked for it instead of trusting windows doing its job, haha, would have saved me the time searching it in Edge APIs,haha. Anyhow thx, its what I am exactly looking for.

joshuacarino_2-1631897064849.png