# Shadow APIs

Suppose an API appears in the production environment but is absent in the documentation. This 'shadow API' scenario poses several challenges:

1. **Incomplete Security Assessments:** The API may not undergo necessary security assessments, leading to incomplete security coverage and potential vulnerabilities going unnoticed.
2. **Limited Visibility:** The absence of documentation restricts visibility, making it challenging to monitor and manage the complete API landscape.
3. **Risk of Undetected Changes:** Without comprehensive coverage, changes made to the API in the production environment may go unnoticed, posing a risk of undetected alterations.
4. **Operational Challenges:** Incomplete documentation hinders efficient operation, as developers may lack crucial information required for successful integration.
5. **Compliance Risks:** The presence of 'shadow APIs' may impact regulatory compliance efforts, as documentation completeness is crucial for assessments.

**Managing Implications**: Conduct thorough audits, document shadow APIs, and implement governance to align production with intended API landscapes.

<figure><img src="/files/KXX5TOhEFcfXf4FhfweX" alt=""><figcaption><p>Shadow API</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pynt.io/documentation/api-catalog/manage-api-source-gaps/shadow-apis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.