What are Sophiie's API rate limits?

Every Sophiie API key allows 60 requests per minute. Go over it and the API returns 429 Too Many Requests with a single Retry-After header telling you how many seconds to wait before trying again.

The 60 per minute is one shared budget per key, and it's spent the moment your key is verified — before your request reaches any endpoint. Reads, writes and cancels all draw from the same allowance, so a client polling once a second burns the whole budget on its own and then gets 429 on its next write.

Steps

If you're hitting 429s:

1. Read the response message. "Rate limit exceeded. Please try again later." means you've spent your 60 per minute. "Plan usage exceeded." means your plan's usage ceiling — slowing down won't fix that one (see Common Questions).
2. Wait the number of seconds in the Retry-After header, then retry. It defaults to 60 when no reset time is known, and is never less than 1.
3. Build request throttling and exponential backoff into your application so you stay under the limit in normal running.

Other limits worth knowing

• Agent tasks: starting an agent task is capped at 10 per organisation per minute, in a fixed 60-second window, on top of your key's 60 per minute. This cap is per organisation, not per key — a second key won't lift it. Refused requests also carry Retry-After.
• Request size: request bodies are capped at 1 MB.
• API keys are managed at Settings → Workspace → API token.

Common Questions

Can I get a higher rate limit?

No. The limit is fixed at 60 requests per minute for every key on every plan, and it can't be raised — there's no request process for a higher limit.

Why am I still getting 429 after backing off?

Check the response message. If it says "Plan usage exceeded.", the 429 is about your plan's usage ceiling, not your request pacing — no amount of throttling clears it. Ask Sophiie Assistant in your dashboard about your plan usage.

Do read-only requests count towards the limit?

Yes. The budget is spent during key verification, so the API can't tell reads from writes — every authenticated request costs one from the same 60.

Why don't I see X-RateLimit-Remaining headers?

They don't exist on Sophiie's API. The only rate-limit header is Retry-After, and it only appears on a 429 response — pace your requests client-side rather than reading headers.

Need More Help?

If you're stuck on a rate-limit problem in your integration, ask Sophiie Assistant in your dashboard first — she can guide you through it. Still stuck? Email support@sophiie.ai or call +61 7 5620 4640.