API Governance
API Governance focuses on Boomi API services and their deployment posture across environments.
What This Feature Answers
Section titled “What This Feature Answers”- How many APIs are visible to the configured Boomi identity?
- Which APIs are drifted between environments?
- Which APIs are undocumented?
- Is APIM plan data available, unavailable, or partially enriched?
Core Signals
Section titled “Core Signals”- Total APIs counts visible API service rows.
- Drifted APIs counts API services with environment differences.
- Undocumented APIs identifies rows missing documentation evidence.
- APIM Plans reflects available APIM enrichment when the tenant and identity allow it.
Typical Workflow
Section titled “Typical Workflow”- Open API Governance.
- Review totals before drilling into rows.
- Read any governance info or source warning before interpreting APIM plan counts.
- Use the table to compare API deployment versions and drift across environments.
Interpretation Tips
Section titled “Interpretation Tips”API Governance can still be useful when APIM endpoint data is unavailable. In that state, BoomiSight keeps Platform API-derived rows visible and explains which indicators are inferred from runtime deployment data.