Too many requests. The 429 on this endpoint can be returned by either of two independent throttles. Both set the Retry-After header, whose value is the number of seconds the client must wait before retrying. The response body contains only a human-readable message.
The global per-tenant Public API rate limiter. Inspect the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers and back off until the window resets.
Repeated failed remote-start attempts on the same EVSE by the same user activate a short cooldown that protects charge points from excessive retried start requests. While the cooldown is active, further session-start calls for that user/EVSE pair are rejected with a 429 Too Many Requests response.
What triggers it. Every failed remote-start attempt against an EVSE — for example, the charge point rejecting the start command, the start request timing out, the EVSE being occupied, or the EV not being connected to the EVSE — counts toward the cooldown for the (user, EVSE) pair that issued the request. Up to two consecutive failures keep the cooldown at the standard 30 seconds; three or more escalate it to 120 seconds.
Scope. The cooldown is scoped strictly to the (user, EVSE) pair that produced the failures — other users on the same EVSE and the same user on a different EVSE are unaffected. Successful starts reset the cooldown counter for that pair.
