Rate limiting and protection against abuse

Preventing a single integration from overloading the platform

To protect Leafy Energy's stability, the demo uses a conceptual rate limiting layer. This makes it easy to explain what happens when usage spikes.

Example limits

• Up to 100 requests per minute per API key.
• Up to 10 concurrent calls per customer for heavy endpoints.

Behaviour when limits are exceeded

• The API returns HTTP 429 Too Many Requests.
• The response includes a retry_after_seconds hint.

{
  "error": {
    "code": "rate_limit_exceeded",
    "retry_after_seconds": 30
  }
}

Demo integrations can show how a client uses backoff instead of continuously hammering the API.