# 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="https://3462681674-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKwBF6q0tAGXlIih38HL%2Fuploads%2Ftpzot8zt8F3KYpdi3Agd%2Fimage.png?alt=media&#x26;token=6e8e7cfc-ed37-4fb2-911d-288dfc971ec3" alt=""><figcaption><p>New API</p></figcaption></figure>