---
title: Per API blocking
description: ASE can be configured to selectively block on a per API basis by configuring an API JSON file parameter.
component: pingintelligence
version: 5.1
page_id: pingintelligence:api_security_enforcer:pingintelligence_per_api_blocking_inline
canonical_url: https://docs.pingidentity.com/pingintelligence/5.1/api_security_enforcer/pingintelligence_per_api_blocking_inline.html
revdate: May 28, 2024
---

# Per API blocking

ASE can be configured to selectively block on a per API basis by configuring an API JSON file parameter.

To enable per API blocking for each API, set the `enable_blocking` parameter to `true` in the API JSON. For example:

```
api_metadata": {
 "protocol": "http",
 "url": "/",
 "hostname": "*",
 "cookie": "",
 "cookie_idle_timeout": "200m",
 "logout_api_enabled": false,
 "cookie_persistence_enabled": false,
 "oauth2_access_token": false,
 "apikey_qs": "",
 "apikey_header": "",
 "enable_blocking": true,
 "login_url": "",
 "api_mapping": {
 "internal_url": ""
 },
```

If per API blocking is disabled, ABS still detect attacks for that specific API, however, ASE does not block them. ASE will continue to block attacks on other APIs with the `enable_blocking` set to `true`.