Impact GateReview changes
Explore APIs and callers
Inspect discovered endpoints, request and response schemas, caller evidence, and contract change history.
On this page
Find an endpoint#
Open API usage
Go to API usage. The table lists HTTP method, endpoint path, provider service, static callers, runtime coverage, and criticality.
Search or filter
Use Search APIs and services to find a method, path, or service. Select a service in the filter to narrow the table; choose Clear to reset it.
Select the endpoint
Choose its path to open the endpoint detail panel below the table.
Inspect endpoint details#
| Tab | What it shows | How to use it |
|---|---|---|
| Overview | Provider service, static caller count, runtime state, criticality/confidence, source, and available schemas. | Check the contract source and inspect the request/response shape. |
| Callers | Detected caller services, evidence type, confidence, and source references. | Follow the caller source to review the relationship and field usage. |
| Change history | Recorded findings associated with this endpoint and links to their pull requests. | Review previous detected contract changes in the retained history. |
A source reference includes a file, line, and commit SHA. GitHub opens the recorded commit rather than the latest branch, so the evidence remains tied to the snapshot or analysis that produced it.
The displayed request and response schemas are extracted from supported documents. Complex or unsupported schema constructs can leave analysis incomplete. Review the repository's Coverage notes when an expected schema or endpoint is missing.
Interpret usage and confidence#
Static callers counts detected relationships in selected indexed repositories. It does not measure traffic volume or capture every deployed consumer. A relationship inferred from a unique endpoint path still requires verification of the deployment host association.
| Runtime label | Meaning |
|---|---|
| Runtime not connected | No runtime observation source is connected; production usage is unknown. |
| No observations in window | The data model has no observation in its relevant window; this alone cannot establish non-use. |
| Observed callers | The data model contains runtime caller observations, when a deployment supports that integration. |