Skip to content
RemindCash

Rate limits

How many requests each API key can make and how to handle 429 responses.

Public API status

The v1 API described here is implemented and tested, but api.remindcash.com is not yet open to the public. It opens after final acceptance testing; until then requests return 503. Examples use placeholders — never paste a real key into shared code.

Limits

Each API key can make 60 requests per minute. The limit is counted per key, so separate keys have separate budgets.

Plan-level API request allowances are part of the Basic and Pro plans; they are not yet enforced or reported through the API.

When you hit the limit

The API responds with 429 Too Many Requests, the standard error body and a Retry-After header with the number of seconds to wait.

JSON
{
    "error": {
        "code": "rate_limited",
        "message": "Too many requests."
    },
    "request_id": "0c998db5-ab69-49f5-8058-227973e19dbc"
}

Staying within the limit

  • Wait for Retry-After before retrying, and add jitter if several workers share a key.
  • Use per_page up to 100 to read more items per request.
  • Give separate systems separate keys so one busy integration does not slow down another.