Catch breaking response changes
Track the fields your app needs instead of only checking whether an endpoint returns HTTP 200.
API and dependency monitoring
Keep API contracts and vendor incidents on the same board.
Dashy packages JSON contract checks, required fields, third-party status feeds, component degradation, incidents, and maintenance windows as scheduled dashboard signals.
API board
contract + vendor
Health APIpassstatus field ok
Billing vendorminor1 incident
Auth JSONmatchversion present
Search APIbreakid missing
Maintenance2scheduled windows
- Contracts
- Fields checked
- Dependencies
- Status feeds
- Reports
- Incident context
Probe
Fetch public JSON endpoints and vendor status summaries with safe, scheduled HTTP checks.
Validate
Check required fields, parse state, expected values, incidents, and maintenance windows.
Explain
Separate internal API breaks from third-party degradation so support teams know who is affected.
Publish
Show contract and dependency state on boards, public status pages, displays, and client reports.
Dashboard components
Show whether the service works and whether the services it depends on are healthy.
- JSON contracts
- Required fields, expected values, parse failures, breaking response shape, and public evidence.
- Dependency status
- Statuspage-style summaries, active incidents, maintenance windows, affected components, and severity.
- API health
- HTTP status, response time, final URL, content type, JSON body checks, and alert-ready state.
- Business context
- Client reports and public dashboards can explain whether the fault is internal, vendor-related, or a contract break.
Trust boundary
Check public endpoints and vendor feeds without turning Dashy into a broad API crawler.
API and dependency boards should stay scoped to explicit public URLs, retained check evidence, and owner-reviewed public output.
- Explicit endpoints
- JSON contract checks run against the public URL and field path the operator enters or approves during quick start.
- Vendor feeds
- Dependency checks read Statuspage-style summaries and component state; they do not scrape private portals or customer-only incident pages.
- Stored evidence
- Dashy stores status, timing, parse result, contract match, incident state, and maintenance-window context for dashboard history.
- Public sharing
- Shared boards should expose pass, warning, failed, and vendor-context summaries, while raw response bodies stay inside the workspace.
Know when a vendor is the cause
Put Stripe, GitHub, cloud, email, search, and other dependency status beside your own checks.
Explain incidents without guesswork
Use client-safe reports that distinguish uptime, API contract, and third-party dependency failures.
Start with public JSON and dependency checks, then save the important signals.
JSON contract and dependency status tools can inspect a target immediately. Quick start turns useful findings into scheduled dashboard components.