Memojin
Log in

Rate limits

120 requests a minute per organization, 100 a day in the sandbox: the RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and Retry-After headers.

api.memojin.com/v1 · Contract 1.0.0-beta.2 · Beta

Sections · Rate limits
On this page
  1. Headers
  2. Beyond the limit
  3. Other limits
  4. Saving requests

Each organization may make 120 requests a minute per environment, shared by all its keys. Every response tells you where you stand.

Headers

Response headers
RateLimit-Limit: 120
RateLimit-Remaining: 117
RateLimit-Reset: 42
  • RateLimit-Limit: requests allowed in the one-minute window.
  • RateLimit-Remaining: requests left.
  • RateLimit-Reset: seconds until the next window.

Beyond the limit

The API answers 429 rate_limited with Retry-After, in seconds. Wait that long, then resume; exponential backoff with jitter is welcome. Spread bulk jobs out rather than running them in parallel.

Response 429
{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests for this organization. Retry after the delay given by `Retry-After`.",
    "details": {
      "retryAfter": 42
    }
  }
}

Other limits

  • Sandbox: 100 requests a day per organization, reset at midnight UTC (429 test_quota_exceeded).
  • A safety net of 600 requests a minute per IP address protects the API before the key is even read.
  • Bodies of at most 1 MB (413).
  • AI generations: bounded by the account’s AI credits (402 insufficient_credits).
  • Need more? Write to contact@memojin.com with your expected volume.

Saving requests

Revalidate your reads with If-None-Match rather than reading everything again, ask for pages of 100 items for a full pass, and poll a generation job every 5 seconds, not more often.