---
title: Basic example
description: The following example configuration demonstrates how request URIs are mapped to the outbound path to alter policy requests.
component: pingauthorize
version: 10.1
page_id: pingauthorize:pingauthorize_server_administration_guide:paz_example_request_uri_outbound_path
canonical_url: https://docs.pingidentity.com/pingauthorize/10.1/pingauthorize_server_administration_guide/paz_example_request_uri_outbound_path.html
revdate: January 25, 2023
---

# Basic example

The following example configuration demonstrates how request URIs are mapped to the outbound path to alter policy requests.

| Gateway API Endpoint property | Example value                               |
| ----------------------------- | ------------------------------------------- |
| `inbound-base-path`           | `/accounts/{accountId}/transactions`        |
| `outbound-base-path`          | `/api/v1/accounts/{accountId}/transactions` |
| `policy-request-attribute`    | `foo=bar`                                   |

A request URI with the path `/accounts/XYZ/transactions/1234` matches the inbound base path and is mapped to the outbound path `/api/v1/accounts/XYZ/transactions/1234`.

The following properties are added to the policy request:

* `HttpRequest.ResourcePath : 1234`

* `Gateway.accountId : XYZ`

* `Gateway.foo : bar`