---
title: PingAccess agent protocol flow
description: The PingAccess agent protocol has a set flow by which requests from clients are evaluated and managed.
component: pingaccess
version: 9.0
page_id: pingaccess:agents_and_integrations:pa_agent_protocol_flow
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/agents_and_integrations/pa_agent_protocol_flow.html
revdate: February 6, 2023
section_ids:
  processing-steps: Processing steps
---

# PingAccess agent protocol flow

The PingAccess agent protocol has a set flow by which requests from clients are evaluated and managed.

The PingAccess agent protocol starts with the client, such as a web browser, OAuth client *(tooltip: \<div class="paragraph">
\<p>The application in an OAuth framework that requests access to resources. If the request is approved by the authorization server, the client is issued an access token for the resources.\</p>
\</div>)*, or any type of HTTP client, making a request for an application resource. The agent sits in front of the resource and intercepts the request. To determine what to do with it, the agent forwards a portion of the request to PingAccess. The response from PingAccess instructs the agent whether to allow the original request, as well as any additional actions to take prior to handing it off to the application. It also includes instructions for actions to perform before sending the corresponding response.

![Flowchart of the agent protocol, showing interactions between client, agent, and according to the following steps.](_images/ngp1565633631738.png)

## Processing steps

1. The client makes a request to the agent system.

2. The agent requests guidance from PingAccess.

3. PingAccess sends a response to the agent.

4. The client request is modified according to any instructions sent by PingAccess.

5. Finally, the client receives a response to their initial request.