We released an updated version of the Apigee UI. ParsePayload policy and payload operations matching in the Apigee UI

## Announcement Announcement On July 6, 2026, we released an updated version of the Apigee UI. ## Feature Feature **ParsePayload policy and payload operations matching in the Apigee UI** The Apigee UI now supports the new payload operations matching feature: * The new **ParsePayload** policy is now available in the proxy editor for API proxy authoring. You can use it to extract logical operations from structured payloads at runtime. * The API Product page now displays payload-based operations, allowing you to configure and manage access control and quotas based on request payload content. For more information, see [Manage MCP tool access with API products](https://cloud.google.com/apigee/docs/api-platform/apigee-mcp/manage-mcp-tool-access). ## Feature Feature **Support for payload operations matching in API Products** Apigee now supports payload operations matching (`payloadOperationGroup`) in API Products, powered by the new **ParsePayload** policy. Payload operations matching allows you to define API Product operations that match fields within request payloads, such as JSON-RPC requests used by the Model Context Protocol (MCP). Apigee can then route, monetize, authorize, and apply distinct quota limits to traffic based on the derived payload operation. This feature is available to all Apigee X customers in all supported regions with no additional charge. For more information, see [Manage MCP tool access with API products](https://cloud.google.com/apigee/docs/api-platform/apigee-mcp/manage-mcp-tool-access)and the [ParsePayload policy reference](https://cloud.google.com/apigee/docs/api-platform/reference/policies/parse-payload-policy).