# Manage API Source Gaps

In various scenarios, attention is warranted when **gaps** exist between your **API sources**.&#x20;

Consider the following situations: [New APIs](https://docs.pynt.io/documentation/api-catalog/manage-api-source-gaps/new-apis), [Untested APIs](https://docs.pynt.io/documentation/api-catalog/manage-api-source-gaps/untested-apis), [Shadow API in Production](https://docs.pynt.io/documentation/api-catalog/manage-api-source-gaps/shadow-apis) or [Undocumented APIs](https://docs.pynt.io/documentation/api-catalog/manage-api-source-gaps/undocumented-apis). Each scenario has unique implications, requiring individualized handling for a comprehensive workflow.

To ensure a robust API security strategy, it is crucial to address and rectify such gaps by [adding all available sources](https://docs.pynt.io/documentation/applications-view/manage-sources-for-api-discovery). This approach allows Pynt to proactively track APIs, ensuring both security and operational insights are comprehensive and accurate.

Gain valuable **insights** into your API landscape with the API Catalog Insights, empowering you to effectively manage and bridge gaps within your API ecosystem.

<figure><img src="https://3462681674-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKwBF6q0tAGXlIih38HL%2Fuploads%2FJPMHqqTpJeeCUZxYujcd%2Fimage.png?alt=media&#x26;token=6234e753-551d-415d-a98d-667b67e2f688" alt=""><figcaption><p>API Catalog insights</p></figcaption></figure>
