Legacy API
Compatibility notes for the original Statance agent and API endpoints, which remain supported.
Statance keeps the original API on api.statance.com so agents and scripts written against it keep working. New integrations should use the v1 REST API.
Agent endpoints
PUT /receive/system/{general,cpu,memory,disk,network,processes,addons} with JSON bodies containing userToken (your API key) and token (per-server token). Data from separate requests in the same minute is merged.
Dashboard endpoints (session cookie)
GET /distribute/servers,/distribute/server?serverId=GET /distribute/graph/{cpu,memory,disk,network}?serverId=&days=GET /distribute/list/processing?serverId=,/distribute/list/recent-alerts?serverId=GET /distribute/recipients,/distribute/alertsPOST /receive/alerts/{submit,update,delete},/receive/recipients/{submit,update,delete},/receive/server/delete
Account endpoints
/account/{login,register,logout,info,plans,change-plan,change-settings,change-key,delete,forgot-password} and /stripe/{create-checkout-session,portal,setup}.
Agent downloads
https://dashboard.statance.com/agent/dl/statance.sh— now installs the current agent while keeping the server tokenhttps://dashboard.statance.com/agent/versions.jsonand/agent/dl/latest.zip— used by the original agent’s auto-updater
Differences
- reCAPTCHA is no longer required on
/account/loginand/account/register; requests are rate limited instead. - The old dashboard at
dashboard.statance.comredirects to the new app atstatance.com/app. - Graph history is limited by your plan’s retention.