# New APIs

When new APIs are on the verge of deployment or are about to arrive in the production environment, there are notable considerations:

1. **Visibility Challenges:** New APIs may not be immediately visible in the catalog, particularly if they are yet to be officially deployed. This may require prompt integration into the API tracking system.
2. **Security Gaps:** Until officially added to the security testing regimen, new APIs may contain potential security gaps, necessitating swift assessment before they become operational.
3. **Operational Impact:** Developers may not be aware of newly introduced APIs, especially if they are in the pre-production phase. This lack of awareness can lead to potential operational challenges without comprehensive documentation.
4. **Ensuring Documentation Completeness:** New APIs may lack complete documentation until they are officially deployed. Proactively addressing documentation gaps ensures that developers have the necessary information for successful integration.

**Managing Implications**: prioritize documentation, and collaboration to smoothly integrate new APIs into your ecosystem.

<figure><img src="/files/Vzr86uD3pacpMhvQc3dH" alt=""><figcaption><p>New 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/new-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.