We are in the early stages of rolling out rate limits. No rate limits are currently enforced, but we are monitoring usage patterns and will implement fair-use protections soon. When enforcement is introduced, this page will be updated to reflect:
  • The exact request limits per minute/hour
  • Which endpoints or operations are affected
  • How to identify when you’re being throttled
  • How to handle rate limit errors gracefully
To ensure reliability and fairness across all partners, the Ownright Developer Platform implements rate limiting — a set of controls that prevent any one client from overwhelming the system. These limits help us maintain:
  • ✅ Fast and consistent performance for all partners
  • 🔐 Protection against accidental or malicious overuse
  • 📈 Platform scalability as usage grows

​
🧠 How to handle rate limits (future)

When limits are enforced, you’ll receive a 429 Too Many Requests response if you exceed them. We will include headers like:
HeaderHTTP Status
Retry-AfterNumber of seconds to wait before retrying
X-Ownright-RateLimit-LimitYour current rate limit
X-Ownright-RateLimit-RemainingHow many requests you have left
X-Ownright-RateLimit-ResetTimestamp when the limit resets
Your app should monitor these headers and implement backoff logic where possible.
Limits apply per API client, not globally across all partners.

​
💬 Need higher limits?

If you expect higher volume or have batch processing needs, reach out to our team ([email protected]). We’re happy to review your use case and adjust limits accordingly.

​
🔒 Reminder

Even in the absence of hard limits, we log and monitor usage to ensure platform health. Please avoid excessive polling and always use webhooks for real-time updates.