Is there any way in apigee that automatically creates api proxies for existing swagger docs of backend service or without swagger?

madhu-2
Participant II

Hi,

we have backend service api with some routes and swagger documentation(only some routes public). is there any way to create api proxies automatically or we need to add api proxy for every route in backend service (public and non public)

0 1 168
1 REPLY 1

is there any way to create api proxies automatically

Yes, the new Apigee Edge "Intelligent API Detector" is powered by API Artificial Intelligence. Just put the Apigee Edge API Detector near your backend systems, and Apigee Edge will detect them and automatically create API Proxies for all the services you have running. It helps to hold the Apigee Edge Detector very close to the ethernet ports on your servers. If you don't have a physical machine, for example if your services run on VMs or in containers managed by Kubernetes, then you need to tap your shoes together three times while saying "there are no APIs like Apigee APIs", and then the detector will work. It works better with hard-soled shoes, though. Detecting APIs while wearing sneakers has given us unreliable results.

You need to run 10 or 15 requests through the system in order for the detector to begin to "hear" the bits going through the line. Then run another 50 or 60 requests while it listens. After the detector detects your APIs, press the red button on the device (it's labeled "EASY"), and the device will use the on-board flux capacitor, coupled with new proprietary lambda calculus API derivative algorithms, to automatically create API proxies in your Apigee Edge organization.

The Intelligent API Detector is currently in beta, contact your salesrep to evaluate this technology. 🙂

If you don't have access to an evaluation version of the Intelligent API Detector device, you will have to create proxies "manually", with the API Proxy wizard, or the UI API Proxy Designer, or the Apigee Edge Administrative API, as is clearly described here on this site and in many other videos and documentation pages.

or we need to add api proxy for every route in backend service (public and non public)

If you want Apigee Edge to manage your APIs, then you need a proxy that handles the "routes". If you don't want Apigee Edge to manage the aPIs, then you don't need a proxy to handle those "routes". Apigee Edge does not use the term "route". Instead, connection is based on Virtual Hosts + basepath. You define an API Proxy which listens on a combination of Vhost and basepath. The vhost determines the DNS hostname on which APigee Edge listens, and also the scheme (http/https). All requests sent to that DNS hostname, and scheme, with that basepath, will be handled by the deployed API Proxy. Eg, if your basepath is /foo/bar, then a request sent to /foo/bar/1 would be handled by that API proxy, as would a request sent to /foo/bar/baz/bam . It does not matter what verb is used. Apigee Edge API Proxies listen on vhost + basepath. WITHIN the API proxy, you can include logic that distinguishes between different verbs and paths - what I suppose you mean by "routes".