Why it matters
- Organisations rarely know the full API estate.
- APIs can exist outside gateways, documentation, ownership and normal testing.
- You cannot validate API abuse paths until the API surface is visible.
API Discovery
Discover internal, external, documented and undocumented APIs across gateways, specs, logs, repositories and exposed services.
Evidence traceApproved scopeTarget-aware testing
Capability architecture
Find the route that documentation and gateways missed.
ThreatCanary correlates external discovery, traffic, specifications and code context to identify reachable API endpoints.
ThreatCanary approach
- Identify APIs from external reconnaissance, traffic metadata, API gateways, OpenAPI specs and platform integrations.
- Classify REST, GraphQL and other API-like services where supported.
- Store endpoints, methods, evidence, confidence and relationships in the graph.
What it validates or reveals
- External APIs, internal APIs and undocumented endpoints.
- Exposed API documentation and gateway-discovered services.
- API surface that needs ownership, mapping or testing.
Evidence produced
- Observed route, method and host evidence.
- Discovery source and confidence.
- Authentication behaviour, owner and downstream relationship.
Evaluate the capability
Book a product walkthrough