> Source: [sk184006](https://support.checkpoint.com/results/sk/sk184006)

# sk184006 - API Discovery shows PII findings but does not identify the responsible endpoint

| Property | Value |
|----------|-------|
| Solution ID | sk184006 |
| Date Created | 2026-06-14 |
| Last Modified | 2026-06-17 |
| Technical Level | General |
| Products | WAF Application Security |
| Versions | Cloud |

## Symptoms

- API Discovery shows endpoints with PII (Personally Identifiable Information) findings but does not show which specific endpoint contains the PII data.

## Solution

Configure API Discover with accurate definitions. Follow the guidelines below.

**API Discovery Asset Setup**

1. Open `Check Point Portal` \> `WAF Application Security` \> `Assets`.
2. Create two assets for API Discovery
   * Base application - for example:   
     `example.com`
   * API calls - for example:  
     `example.com/api`
3. Verify that the API URL matches the actual API path.

**Correct Application Response Codes**

Ensure that the application returns appropriate HTTP response codes.

API Discovery relies on response codes in the 200-399 range to learn endpoints. Misconfiguration causes the system to incorrectly identify and learn non-existent APIs, preventing it from accurately pinpointing endpoints storing PII.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content