How to create policy?


Welcome to the Young App Platform (YAP)!
In this tutorial, we’ll walk you through the building and testing a policy example within the Young App platform.
YAP provides certain built-in policies, which can be referred to address general situations to filter unwanted traffic coming to your API or transform output data on your response. Also, YAP allows creating custom policies, which are designed primarily to address complex scenarios like SQL injection.
Policies are applied inside the gateway located between the consumer API and the YAP's API. The gateway receives all requests and usually forwards them unchanged to the underlying API. However, a policy can apply changes to both: the inbound request and outbound response.

Policy configuration

The policy definition is a simple XML document that describes a sequence of inbound and outbound statements. The XML can be edited by the customer's developer directly in the definition window. A list of statements is provided by YAP. The statements applicable to the current scope are enabled and highlighted.
The configuration is divided into inbound, outbound, and on-error.
The series of specified policy statements are executed in a request-response order.
<!-- statements to be applied to the request go here -->
<!-- statements to be applied to the response go here -->
<!-- statements to be applied if there is an error condition go here -->
If there is an error during processing of a request, any remaining steps in the inbound, or outbound sections are skipped and execution jumps to the statements in the on-error section.
By placing policy statements in the on-error section, you can review the error by using the context.LastError property, inspect and customize the error response using the set-body policy, and configure what happens if an error occurs.
To see error codes for built-in steps and for errors that may occur during the processing of policy statements, visit Error handling in API management.


Apply policies specified at different scopes.
YAP allows determining the order of combined policy statements.

My custom policy

import { Context, ExecutionContext, IPolicy, tryExecuteFieldValue, YapPolicy } from "@youngapp/yap";
id: 'example-policy',
name: 'Example policy',
category: 'security',
description: 'The example-policy policy to set the message body for incoming and outgoing requests.',
scopes: ['inbound', 'outbound', 'on-error']
export class ExamplePolicy implements IPolicy {
* example-policy policy
* Use the example-policy policy to set the message body for incoming and outgoing requests.
* To access the message body you can use the context.request.body property
* or the context.response.body, depending on whether the policy is in the inbound or
* outbound section.
* @example
* <example-policy>bJtrpFi1fO1JMCcwLx8uZyAg</example-policy>
public async apply(executionContext:ExecutionContext) {
const { policyElement, context, scope } = executionContext;
context.request.body = tryExecuteFieldValue(policyElement.elements[0].text, executionContext);
return executionContext;
public validate(policyElement: any) {
return true;

How to use my policy ?

import { Yap } from "@youngapp/yap";
import { ExamplePolicy } from "./policies/ExamplePolicy.ts";
const app = new Yap();
// Add ExamplePolicy in Application
// ...
export default app