---
title: Advanced example
description: 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_request_uri_outbound_path
canonical_url: https://docs.pingidentity.com/pingauthorize/10.1/pingauthorize_server_administration_guide/paz_request_uri_outbound_path.html
revdate: January 25, 2023
---

# Advanced example

Request URIs are mapped to the outbound path to alter policy requests.

Consider the following example configuration.

| Gateway API Endpoint property | Example value                            |
| ----------------------------- | ---------------------------------------- |
| `inbound-base-path`           | `/health/{tenant}/{resourceType}`        |
| `outbound-base-path`          | `/api/v1/health/{tenant}/{resourceType}` |
| `service`                     | `HealthAPI.{resourceType}`               |
| `resource-path`               | `{resourceType}/{_TrailingPath}`         |

A request URI with the path `/health/OmniCorp/patients/1234` matches the inbound base path and is mapped to the outbound path `/api/v1/health/OmniCorp/patients/1234`.

The following properties are added to the policy request:

* `service : HealthAPI.patients`

* `HttpRequest.ResourcePath : patients/1234`

* `Gateway.tenant : OmniCorp`

* `Gateway.resourceType : patients`