An API Policy record can only be associated with a single API Frontend, even if multiple API Frontend records are linked to the same API Policy.<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue: Starting from 2.1 version, the system creates multiple API Frontend records with different hostnames and HTTP methods for the same Route ID. However, an API Policy can only be linked to one API Frontend record. Refer to the screenshot below, which shows a single API Policy linked to a single Frontend. Reason: The API Policy (api_police) table Reference field is the API Gateway, and its Criterion attribute is the ID. Due to this design, the API Policy table creates only a single entry (record) for each combination of API Gateway and ID values. As a result, when multiple API Frontend records share the same Route ID, only one of them can be associated with an API Policy.