OverviewCopied!

This document outlines the rate limiting policies applied to Electric Era's API to ensure fair usage, maintain system performance, and prevent abuse. Rate limits restrict the number of API requests a client can make within a specified time period. Exceeding these limits results in an HTTP 429 Too Many Requests response. Rate limits are set at Electric Era's sole discretion and may vary based on account type, usage patterns, or other factors. This guide provides details on the rate limit structure, how to monitor usage, and best practices for managing requests.

Rate Limit StructureCopied!

Electric Era's API employs a fixed-window rate limiting mechanism, where limits are applied per client based on their API key or IP address (for unauthenticated requests). Rate limits are defined by the number of requests allowed within a given time window, as determined by Electric Era.

Endpoint-Specific Limits

Certain endpoints may have distinct limits due to their computational complexity or resource intensity. These may be documented in the respective endpoint's API reference or communicated directly to clients.

Handling Rate Limit ExceedancesCopied!

When a client exceeds the rate limit, the API returns an HTTP 429 Too Many Requests status code. To resolve this:

1. Check the Retry-After header to determine how long to wait before retrying.

2. Implement exponential backoff in your application to retry requests after the specified delay.

3. Contact Electric Era support if you frequently encounter rate limit issues to discuss your usage needs.

Best PracticesCopied!

To effectively manage API rate limits and ensure smooth integration, follow these recommendations:

• Cache Responses: Store frequently accessed data locally to reduce the need for repeated API calls.

• Batch Requests: Use bulk endpoints where available to combine multiple operations into a single request.

• Implement Backoff: Use exponential backoff with jitter for retrying requests after receiving a 429 response.

• Optimize Queries: Limit the scope of data requested (e.g., use filters or pagination) to minimize resource-intensive calls.

• Authenticate Requests: Use API keys for authenticated requests to benefit from potentially higher rate limits compared to unauthenticated requests.

• Contact Support: For high-volume use cases, reach out to Electric Era's support team at support@electricera.tech to discuss your requirements.

Frequently Asked QuestionsCopied!

What happens if I exceed the rate limit?

You will receive a 429 Too Many Requests response with a Retry-After header indicating how long to wait before retrying. Your application should respect this delay to avoid further errors.

Can I increase my rate limits?

Rate limit adjustments are at Electric Era's discretion. Contact our support team at support@electricera.tech to discuss your needs.

Do rate limits apply to all endpoints equally?

No, some endpoints may have specific limits based on their resource demands. Check the API reference or your account details for endpoint-specific information.

How are rate limits enforced for unauthenticated requests?

Unauthenticated requests are limited by the client’s IP address, which typically has lower quotas than authenticated requests using an API key.