Chargefox API Rate Limiting

To ensure fair usage and system stability, the Chargefox API implements rate limiting on its endpoints. Rate limiting restricts the number of API requests that can be made within a specific time period.

How Rate Limiting Works

---

When you make requests to the Chargefox API, we track the number of requests made with your authentication token. If you exceed the allowed number of requests in a specified time window, you'll receive a 429 Too Many Requests response until the rate limit resets.

Rate Limit Response Headers

When you make a request, the following headers are included in the response:

• X-RateLimit-Limit: The maximum number of requests allowed per period
• X-RateLimit-Remaining: The number of requests remaining in the current period
• X-RateLimit-Reset: The time at which the current rate limit window resets (in seconds)

Best Practices

---

• Implement backoff strategies when you receive a 429 response
• Cache API responses when possible to reduce the number of requests
• Spread out non-urgent requests over time
• Monitor your request volumes and ensure you stay within limits

Fleet API Rate Limits

---

The following rate limits apply to Fleet API endpoints. Each limit is applied per authorization token.

OCPI CPO API Rate Limits

---

The following rate limits apply to OCPI CPO API endpoints. Each limit is applied per authorization token.