# Untested APIs

If an API exists but hasn't undergone security testing, it introduces specific challenges:

1. **Security Blind Spots:** Untested APIs may harbor vulnerabilities or weaknesses that remain undetected, posing a security risk.
2. **Inaccurate Risk Assessment:** Without security testing, the risk assessment may lack crucial insights, potentially leading to misinformed decisions.
3. **Compliance Challenges:** Regulatory compliance often requires thorough security assessments. Untested APIs may create compliance challenges.

**Managing Implications**: Prioritize security assessments, documentation, and collaboration to ensure comprehensive testing and mitigate potential vulnerabilities.

<figure><img src="/files/VpXnlouksSxtrCBaOFGe" alt=""><figcaption><p>Untested 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/untested-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.