Error Codes and Rate Limits

This page outlines the types of errors you may encounter while using the API, along with guidance on how to resolve them.

Error Codes

Reka Research uses standard HTTP status codes to indicate the success or failure of requests. Below is a list of common error codes you may encounter, along with their meanings and suggested resolutions.

Status CodeDescriptionResolution
400The request is missing required parameters or includes invalid ones.Check your request payload and required parameters. Check the API reference for more details.
401The API key provided is missing, invalid, or has been disabled.Go to Reka Platform and get a valid, active API key.
429The account does not have enough credits to complete the request.Go to Reka Platform and add more credits to your account before retrying.
429The request exceeded the allowed rate limit.Wait and retry after some time or reduce request frequency. See Rate Limiting for more details.
500An unexpected server error occurred while processing the request.Try again later. If the issue persists, contact us via Discord.

Rate Limiting

Reka Research implements rate limiting to ensure fair usage and prevent abuse. Each API key has a limit of 60 requests per minute.

When a user exceeds the allowed number of requests in a short time, the API responds with a 429 Too Many Requests error and includes rate-limiting headers to help manage future requests.

Please contact us if you need a higher limit.

Here’s an example response header:

Headers({
'date': 'Mon, 23 Jun 2025 20:32:19 GMT',
'content-type': 'application/json',
'content-length': '48',
'connection': 'keep-alive',
'server': 'uvicorn',
'x-ratelimit-limit': '60',
'x-ratelimit-remaining': '0',
'x-ratelimit-reset': '1750710800.5404356',
'retry-after': '60',
'x-request-id': 'a0bbd491e74c40259c1e72b00ad51b46'
})
HeaderDescription
x-ratelimit-limitThe maximum number of requests allowed in the current window.
x-ratelimit-remainingThe number of requests remaining in the current window.
x-ratelimit-resetThe time (epoch) when the current rate limit window resets.
retry-afterNumber of seconds to wait before making a new request.
x-request-idUnique ID for this request, useful for debugging or support inquiries.

Can’t find what you need?

If you’re having trouble finding the information you need, please reach out to us via Discord for assistance.