SPAN · Rate Limits

Span Io Rate Limits

SPAN API is hosted directly on SPAN Panel — a constrained embedded device on the home LAN. SPAN does not publish formal per-request rate limits. Practical limits are dictated by the panel's CPU, memory, and the embedded MQTT broker's connection capacity. SPAN's documentation strongly RECOMMENDS that clients use the MQTT publish/subscribe surface for high-frequency telemetry rather than polling REST endpoints in tight loops.

Span Io Rate Limits is the machine-readable rate-limit profile for SPAN on the APIs.io network, conforming to the API Commons Rate Limits specification.

The profile also includes 3 backoff/retry policies defined.

Tagged areas include Energy, Home Energy, Electrification, Smart Panel, and Electrical Panel.

0 Limits
EnergyHome EnergyElectrificationSmart PanelElectrical PanelHome AutomationSolarEnergy StorageEV ChargingGridIslandingBackup PowerDemand ResponseIoTMQTTHomieElectrification BusOn-Premise

Policies

No documented hard rate limit. Clients SHOULD avoid polling panel state / circuits at high frequency; use MQTT subscriptions for streaming telemetry. Bursty REST traffic on the panel may degrade responsiveness of the SPAN Home apps.
The panel-hosted MQTT broker has a finite connection capacity. Each registered API client SHOULD use a single long-lived MQTT connection rather than repeatedly reconnecting.
Client registration (POST /api/v1/auth/register) is a setup-time operation. There is no published quota but clients SHOULD register exactly once per integration and persist the returned JWT.