Operate Web Fleet

API and integrations

A documented API is planned, but it will follow the core product model rather than becoming a parallel configuration system.

Planned API shape

# Illustrative future request - not shipped yet
curl -H "Authorization: Bearer $WEBFLEET_TOKEN" \
  https://fleet.example.com/api/v1/sites

Tokens will be scoped, revocable and audited. A tracker/property token must never double as a dashboard API credential.

Deployment events

Web Fleet can become much more useful when it knows when a site was deployed. The initial integration direction is observation: GitHub, webhooks or APIs report a deployment event, then Web Fleet correlates that timestamp with uptime, performance, link and analytics changes.

{
  "site": "nift.dev",
  "environment": "production",
  "revision": "abc1234",
  "status": "deployed",
  "source": "github"
}

Notifications

Email, chat and webhook transports should use one delivery model with retry history, redacted secrets and explicit failure state. Integrations are not an excuse to hide delivery errors.