Rate Limiting

Our API employs rate limiting to ensure fair usage and protect our service from abuse. This document provides information on the rate limits we impose and how you can monitor your current usage.

General Limits for Plans

  • 60 requests per minute

Endpoints with Special Limits

Some specific endpoints may have unique rate limits to ensure the stability of the service. For example:

  • Create Image with create_now option set to true: 10 simultaneous requests

Headers

The following headers in the API response provide information about your current rate limit status:

  • X-RateLimit-Limit: The maximum number of requests allowed in the current time frame.
  • X-RateLimit-Remaining: The number of requests left for the current time frame.
  • X-RateLimit-Reset: The time (in UTC epoch seconds) when the rate limit will reset.

Handling Rate Limits

If you exceed the rate limits, the API will return a 429 Too Many Requests status code.

Best Practices

  • Handle 429 Responses Gracefully: Implement error handling to detect rate limit errors and adjust your request rate accordingly. Consider implementing a retry mechanism with an exponential backoff strategy.
  • Monitor Headers: Always monitor the X-RateLimit-* headers to be aware of your current usage and adapt accordingly.

Increase Rate Limits

We're open to customize these limits for you if you have a specific use case in mind. Please inquire via armin@placid.app