---
title: Configuring discovery settings in the Dashboard
description: To customize the discovery process, configure the discovery parameters on the Dashboard.
component: pingintelligence
version: 5.2
page_id: pingintelligence:getting_started_with_pingintelligence:pingintelligence_configure_discovery_settings
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/getting_started_with_pingintelligence/pingintelligence_configure_discovery_settings.html
revdate: April 3, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
  example: Example:
---

# Configuring discovery settings in the Dashboard

## About this task

To customize the discovery process, configure the discovery parameters on the Dashboard.

## Steps

1. Go to **Discovered APIs → Settings**.

![A screen capture of the Discovered APIs page in PingIntelligence with the Discovered APIs and Settings links highlighted in yellow. Discovered APIs is numbered 1, and Settings is numbered 2 to show the order of your clicks.](_images/hkd1607595182330.png)

1. Click the **Discovery Configuration** tab and set the value for **AI Engine Subpath Depth**.

   **AI Engine Subpath Depth** defines the number of subpaths used to uniquely discover the base path of a new API. The maximum allowed value is 6 when ASE is deployed in inline mode and 10 when ASE is deployed in sideband mode.

   ### Example:

   The following are examples of subpath values and what they mean:

   * `1` indicates `/atmapp` is the base path for `/atmapp/zipcode`,`/atmapp/update`, and so on.

   * `3` indicates `v1/cust1/atmapp` is the base path for `v1/cust1/atmapp/zipcode`, and so on.

2. Click **Discovered APIs** on the Dashboard and click **Export** to download the API definition in `.json` format .

   ![A screen capture of the Discovered APIs page in the PingIntelligence Dashboard with a yellow arrow pointing to Discovered APIs in the left navigation pane and a second yellow arrow pointing to the Export link next to an API definition.](_images/qyl1631090190432.png)

3. Add the downloaded API JSON definitions to ASE by running the following command:

   ```
   # /<ASE_Installation path>/pingidentity/ase/bin/cli.sh –u admin -p admin add_api {file_path/api_name}
   ```