Document authentication, scopes, rate limits, and examples.
Resource · Resources
FTStatus API documentation
Developer-facing documentation for automating monitors, probes, incidents, status pages, and integrations.
Reliable visibility without exposing internal infrastructure.
Keep examples synchronized with live routes.
Fail closed on invalid credentials and insufficient scopes.
Watch the signal
Track the public evidence customers actually experience.
Measure the trend
Keep response, uptime, and incident context close to the decision.
Route the response
Alert the right people and publish customer-safe updates when needed.
API keys
Use scoped API keys for automation and rotate keys from the dashboard when ownership changes.
Probe ingestion
Use authenticated probe payloads for external monitoring locations and WHMCS bridge events.
Webhook events
Document event shape, retry behavior, signatures, and redaction rules before public launch.
Related pages
Continue building the monitoring workflow.
Ready to set up the right monitors?
Start with critical customer-facing services, then add status pages, alert routes, and managed help as reliability becomes more important.
