---
title: Add API definitions to ASE
description: Add the API definition files to help API Security Enforcer (ASE) extract metadata from API traffic, set decoys to trap intruding attacks, perform health checks on backend servers, and so on.
component: pingintelligence
version: 5.2
page_id: pingintelligence:pingintelligence_integrations:pingintelligence_apigee_add_api_definitions
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/pingintelligence_integrations/pingintelligence_apigee_add_api_definitions.html
revdate: May 6, 2024
---

# Add API definitions to ASE

Add the API definition files to help API Security Enforcer (ASE) extract metadata from API traffic, set decoys to trap intruding attacks, perform health checks on backend servers, and so on.

The API definitions also help the artificial intelligence (AI) engine to build AI models to detect any Indicators of Attacks (IoAs) on APIs. After the policy has been deployed to Apigee using the PingIntelligence automated policy tool, add APIs to ASE.

For more information on defining APIs, see:

* [API naming guidelines](../pingintelligence_reference_guide/pingintelligence_api_naming_guidelines.html)

* [Defining an API using API JSON configuration file in sideband mode](../pingintelligence_reference_guide/pingintelligence_define_api_json_file_sideband.html)

For more information on ASE sideband deployment, see [Sideband ASE](../pingintelligence_reference_guide/pingintelligence_sideband_ase.html).