Your APIs
Alerts
View allUnapproved API: Discovered: ip-api.com
03/03 09:32
Unapproved API: Discovered: crt.sh
03/03 09:32
Unapproved API: Discovered: dns.google
03/03 09:32
Unapproved API: Discovered: cloudflare-dns.com
03/03 09:32
New API discovered: ip-api.com
03/02 12:50
APIs your organization publishes and exposes to external consumers
Total APIs
4
3 active, 1 deprecated
Total Consumers
27
Across all APIs
Inbound Calls (24h)
6,779
+12% from yesterday
Consolidation Opps
1
Merge recommended
API Registry
| API | Endpoint | Version | Consumers | Status | Calls (24h) | Actions |
|---|---|---|---|---|---|---|
|
Customer Data API
Core customer records
|
api.acme.com/v2/customers
|
v2.1 | 12 active | Active | 4,231 | |
|
Order Processing API
Order lifecycle management
|
api.acme.com/v1/orders
|
v1.8 | 7 active | Active | 1,847 | |
|
Customer Lookup API
Legacy customer search
|
api.acme.com/v1/cust-lookup
|
v1.2 | 3 active | Deprecated | 89 | |
|
Reporting API
Analytics and reports
|
api.acme.com/v2/reports
|
v2.0 | 5 active | Active | 612 |
Consolidation Recommendations
AI-PoweredSmart analysis of your API surface to identify consolidation opportunities
Merge "Customer Data API" and "Customer Lookup API"
These APIs share 78% endpoint overlap. The Lookup API (v1.2) appears to be a legacy subset of the Customer Data API (v2.1). Only 3 consumers still use the older API.
Unified authentication for "Order Processing" and "Reporting" APIs
Both APIs use different authentication schemes. Standardizing on a single auth pattern would simplify consumer onboarding and reduce key management overhead.