Hosting Environment
Operating System
Task Type
Draft Beta

PingIntelligence for APIs Apigee Integration

Updated 78

Add to MyDocs | Hide Show Table of Contents

PingIntelligence Apigee Integration

PingIntelligence provides a shared flow to integrate Apigee Edge with PingIntelligence for APIs platform. The two mechanisms of calling shared flows are flow callout and flow hook policies. A Flow Hook in Apigee Edge applies the PingIntelligence shared flow globally to all APIs in an environment under an organization. The Flow Call Out policy in Apigee Edge applies the PingIntelligence shared flow on a per API basis in an environment under an organization.

PingIntelligence provides an automated tool to deploy both Flow Hook and Flow Call Out polices.

The following diagram shows the logical setup of PingIntelligence ASE and Apigee Edge:

Here is the traffic flow through the Apigee Edge and PingIntelligence for APIs components.

  1. Incoming request to Apigee Edge
  2. Apigee Edge makes an API call to send the request information to ASE
  3. ASE checks the request against a registered set of APIs and checks the origin IP, cookie, OAuth2 token or API key against the Blacklist. If all checks pass, ASE returns a 200-OK response to the Apigee Edge. If not, a different response code (403) is sent to Apigee Edge. The request information is also logged by ASE and sent to the AI Engine for processing.
  4. If Apigee Edge receives a 200-OK response from ASE, then it forwards the request to the backend server. Otherwise, the Gateway optionally blocks the client.
  5. The response from the backend server is received by Apigee Edge.
  6. Apigee Edge makes a second API call to pass the response information to ASE which sends the information to the AI engine for processing.
  7. ASE receives the response information and sends a 200-OK to Apigee Edge.
  8. Apigee Edge sends the response received from the backend server to the client.

Tags Product > PingIntelligence; Product > PingIntelligence > PingIntelligence 3.2