feat(ai-gateway): Request Tranformer + Request Tranformer Advanced policy overviews by lmilan · Pull Request #7275 · Kong/developer.konghq.com

lmilan · 2026-09-17T13:37:35Z

Description

Preview Links

Checklist

Tested how-to docs. If not, note why here.
All pages contain metadata.
Any new docs link to existing docs.
All autogenerated instructions render correctly (API, decK, Konnect, Kong Manager).
Style guide (capitalized gateway entities, placeholder URLs) implemented correctly.
Every page has a description entry in frontmatter.
Add new pages to the product documentation index (if applicable).

netlify · 2026-09-17T13:37:42Z

✅ Deploy Preview for kongdeveloper ready!

Name	Link
🔨 Latest commit	`ec9af3d`
🔍 Latest deploy log	https://app.netlify.com/projects/kongdeveloper/deploys/6aabf968a95af20008621ba2
😎 Deploy Preview	https://deploy-preview-7275--kongdeveloper.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

cloudjumpercat

Just some nitpicks!

cloudjumpercat · 2026-09-18T20:51:01Z

@@ -1,9 +1,74 @@
 ---
+description: Use powerful regular expressions, variables, and templates to transform API requests


Suggested change

description: Use powerful regular expressions, variables, and templates to transform API requests

descriptions, tags, categories are already autogenerated from the plugin source

cloudjumpercat · 2026-09-18T20:51:11Z

+tags:
+  - transformations
+categories:
+  - transformations


Suggested change

tags:

- transformations

categories:

- transformations

cloudjumpercat · 2026-09-18T21:01:42Z

@@ -0,0 +1,8 @@
+This Policy lets you configure simple transformations of requests before {{site.ai_gateway}} forwards them to the upstream provider. These transformations can be simple substitutions or complex ones matching portions of incoming requests using regular expressions, saving those matched strings into variables, and substituting those strings into transformed requests using flexible templates.


Suggested change

This Policy lets you configure simple transformations of requests before {{site.ai_gateway}} forwards them to the upstream provider. These transformations can be simple substitutions or complex ones matching portions of incoming requests using regular expressions, saving those matched strings into variables, and substituting those strings into transformed requests using flexible templates.

This Policy lets you configure transformations of requests before {{site.ai_gateway}} forwards them to the upstream provider.

These transformations can be simple substitutions or complex ones.

For example, complex transformations can match portions of incoming requests using regular expressions, save those matched strings into variables, and substitute those strings into transformed requests using flexible templates.

cloudjumpercat · 2026-09-18T21:02:30Z

@@ -0,0 +1,8 @@
+This Policy lets you configure simple transformations of requests before {{site.ai_gateway}} forwards them to the upstream provider. These transformations can be simple substitutions or complex ones matching portions of incoming requests using regular expressions, saving those matched strings into variables, and substituting those strings into transformed requests using flexible templates.
+
+This Policy operates on the raw HTTP request only: headers, query string, and body fields. To transform a request based on its meaning, using an LLM (for example, rewriting a prompt), use the [AI Request Transformer Policy](/ai-gateway/policies/ai-request-transformer/) instead.


Suggested change

This Policy operates on the raw HTTP request only: headers, query string, and body fields. To transform a request based on its meaning, using an LLM (for example, rewriting a prompt), use the [AI Request Transformer Policy](/ai-gateway/policies/ai-request-transformer/) instead.

This Policy operates on the raw HTTP request only: headers, query string, and body fields. To transform a request based on its meaning using an LLM (for example, rewriting a prompt), use the [AI Request Transformer Policy](/ai-gateway/policies/ai-request-transformer/) instead.

cloudjumpercat · 2026-09-18T21:10:30Z

+
+{% include md/ai-gateway/v2/policies/request-response-transformer/templates.md %}
+
+## Example


Suggested change

## Example

## Example: Remove Anthropic-specific beta fields

cloudjumpercat · 2026-09-18T21:13:42Z

+
+{% include md/ai-gateway/v2/policies/request-response-transformer/request-transformer-description.md %}
+
+The Request Transformer Advanced Policy provides features that aren't available in the [Request Transformer Policy](/ai-gateway/policies/request-transformer/), including the ability to limit the list of allowed parameters in the request body with the [config.allow.body](./reference/#schema--config-allow-body) parameter.


Suggested change

The Request Transformer Advanced Policy provides features that aren't available in the [Request Transformer Policy](/ai-gateway/policies/request-transformer/), including the ability to limit the list of allowed parameters in the request body with the [config.allow.body](./reference/#schema--config-allow-body) parameter.

The Request Transformer Advanced Policy provides features that aren't available in the [Request Transformer Policy](/ai-gateway/policies/request-transformer/), including the ability to limit the list of allowed parameters in the request body with the [`config.allow.body`](./reference/#schema--config-allow-body) parameter.

cloudjumpercat · 2026-09-18T21:19:18Z

+
+Body transformations are only performed for requests where the `Content-Type` header is set to `application/json`.
+
+## Example


Suggested change

## Example

## Example: Define JSON fields a client can send and move query parameters

cloudjumpercat · 2026-09-18T21:28:34Z

+1. [Rename](./reference/#schema--config-rename)
+1. [Replace](./reference/#schema--config-replace)
+1. [Add](./reference/#schema--config-add)
+1. [Append](./reference/#schema--config-append)


Suggested change

1. [Append](./reference/#schema--config-append)

1. [Append](./reference/#schema--config-append)

1. [Allow](./reference/#schema--config-allow)

Learned this from Hal https://kongstrong.slack.com/archives/C0B913DUBLP/p1789766639575629?thread_ts=1789766632.370589&cid=C0B913DUBLP

migrate policies

dd1dfbe

lmilan self-assigned this Sep 17, 2026

copy edits

ec9af3d

lmilan marked this pull request as ready for review September 17, 2026 14:30

lmilan requested a review from a team as a code owner September 17, 2026 14:30

cloudjumpercat approved these changes Sep 18, 2026

View reviewed changes

Navigation Menu

feat(ai-gateway): Request Tranformer + Request Tranformer Advanced policy overviews - #7275

feat(ai-gateway): Request Tranformer + Request Tranformer Advanced policy overviews#7275
lmilan wants to merge 2 commits into
mainfrom
feat/requst-transformer-policies

lmilan commented Sep 17, 2026 •

edited

Loading

Uh oh!

netlify Bot commented Sep 17, 2026 •

edited

Loading

Uh oh!

cloudjumpercat left a comment

Uh oh!

cloudjumpercat Sep 18, 2026

Uh oh!

cloudjumpercat Sep 18, 2026

Uh oh!

cloudjumpercat Sep 18, 2026

Uh oh!

cloudjumpercat Sep 18, 2026

Uh oh!

cloudjumpercat Sep 18, 2026

Uh oh!

cloudjumpercat Sep 18, 2026

Uh oh!

cloudjumpercat Sep 18, 2026

Uh oh!

cloudjumpercat Sep 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		@@ -1,9 +1,74 @@
		---
		description: Use powerful regular expressions, variables, and templates to transform API requests

		@@ -0,0 +1,8 @@
		This Policy lets you configure simple transformations of requests before {{site.ai_gateway}} forwards them to the upstream provider. These transformations can be simple substitutions or complex ones matching portions of incoming requests using regular expressions, saving those matched strings into variables, and substituting those strings into transformed requests using flexible templates.

-This Policy lets you configure simple transformations of requests before {{site.ai_gateway}} forwards them to the upstream provider. These transformations can be simple substitutions or complex ones matching portions of incoming requests using regular expressions, saving those matched strings into variables, and substituting those strings into transformed requests using flexible templates.
+This Policy lets you configure transformations of requests before {{site.ai_gateway}} forwards them to the upstream provider.
+These transformations can be simple substitutions or complex ones.
+For example, complex transformations can match portions of incoming requests using regular expressions, save those matched strings into variables, and substitute those strings into transformed requests using flexible templates.

		@@ -0,0 +1,8 @@
		This Policy lets you configure simple transformations of requests before {{site.ai_gateway}} forwards them to the upstream provider. These transformations can be simple substitutions or complex ones matching portions of incoming requests using regular expressions, saving those matched strings into variables, and substituting those strings into transformed requests using flexible templates.

		This Policy operates on the raw HTTP request only: headers, query string, and body fields. To transform a request based on its meaning, using an LLM (for example, rewriting a prompt), use the [AI Request Transformer Policy](/ai-gateway/policies/ai-request-transformer/) instead.


		{% include md/ai-gateway/v2/policies/request-response-transformer/templates.md %}

		## Example


		{% include md/ai-gateway/v2/policies/request-response-transformer/request-transformer-description.md %}

		The Request Transformer Advanced Policy provides features that aren't available in the [Request Transformer Policy](/ai-gateway/policies/request-transformer/), including the ability to limit the list of allowed parameters in the request body with the [config.allow.body](./reference/#schema--config-allow-body) parameter.


		Body transformations are only performed for requests where the `Content-Type` header is set to `application/json`.

		## Example

	## Example
	## Example: Define JSON fields a client can send and move query parameters

	1. [Append](./reference/#schema--config-append)
	1. [Append](./reference/#schema--config-append)
	1. [Allow](./reference/#schema--config-allow)

Conversation

lmilan commented Sep 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Preview Links

Checklist

Uh oh!

netlify Bot commented Sep 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for kongdeveloper ready!

Uh oh!

cloudjumpercat left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

lmilan commented Sep 17, 2026 •

edited

Loading

netlify Bot commented Sep 17, 2026 •

edited

Loading