Rate limits

Limit

Ocoya applies a global user rate limit of 60 requests per minute for REST API requests using the same API key. If you expect bursts, queue requests and use a backoff strategy instead of retrying immediately.

Rate Limit Response

When the limit is exceeded, the API returns 429 Too Many Requests.

HTTP/1.1 429 Too Many Requests
Content-Type: application/json
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0

{
  "message": "You've exceeded the request limit."
}

Headers

Header	Meaning
`X-RateLimit-Limit`	Maximum number of API requests allowed per minute.
`X-RateLimit-Remaining`	Remaining number of API requests in the current window.
`X-RateLimit-Reset`	Timestamp indicating when the remaining limit resets.

Recommended Handling

Back off after 429

Wait until the reset window before retrying requests.

Avoid polling aggressively

Prefer event-driven workflows and scheduled jobs over high-frequency polling.

Batch where possible

Reuse workspace and social profile IDs instead of fetching them before every post creation.

Authentication

Limitations

Get Started

Fundamentals

API Reference

Limit

Rate Limit Response

Headers

Recommended Handling

​Limit

​Rate Limit Response

​Headers

​Recommended Handling

Limit

Rate Limit Response

Headers

Recommended Handling