Troubleshooting

Solutions for the most common errors you'll encounter when using the gateway.

401 — INVALID_API_KEY

The API key was not recognized or has been revoked.

Steps to fix:

  1. 1. Go to API Keys and confirm the key has status Active (not Revoked)
  2. 2. Check the request header name is X-API-Key, not Authorization
  3. 3. Confirm the key belongs to the same organization as the model you are accessing
  4. 4. If you recently rotated the key, update all integrations to use the new key

402 — INSUFFICIENT_CREDITS

Your credit balance is lower than the cost of the requested endpoint.

Steps to fix:

  1. 1. Check remaining credits on the Dashboard overview or Billing page
  2. 2. Top up via Billing → Top-up Credits, or upgrade to a plan with a higher monthly quota
  3. 3. Credits reset at the start of each billing cycle — check when your cycle renews

Credits not reserved

Credits are only deducted on successful (2xx) responses. Failed requests do not consume credits.

402 — NO_SUBSCRIPTION

The organization has no active subscription.

Steps to fix:

  1. 1. Go to Billing in the dashboard
  2. 2. Subscribe to any plan — the Free plan is available at no cost

429 — RATE_LIMIT_EXCEEDED

Too many requests in the current 60-second window.

Steps to fix:

  1. 1. Check your plan's limit in the _meta._rate_limits.limit_minute response field
  2. 2. Spread requests across the minute window, or upgrade to a plan with a higher rate limit
  3. 3. Implement exponential backoff in your integration:
Exponential backoff
async function requestWithRetry(fn, maxRetries = 3) {
  for (let i = 0; i < maxRetries; i++) {
    try {
      return await fn()
    } catch (err) {
      if (err?.response?.status === 429 && i < maxRetries - 1) {
        const delayMs = Math.pow(2, i) * 1000
        await new Promise(r => setTimeout(r, delayMs))
      } else {
        throw err
      }
    }
  }
}

502 — Model Session Expired

The connected model's OnlyFans session has expired. Sessions expire after extended inactivity or when OnlyFans invalidates them server-side.

Steps to fix:

  1. 1. Go to Models in the dashboard
  2. 2. Find the affected model — it will show status Disconnected
  3. 3. Click the reconnect (↺) button and re-enter the OnlyFans credentials
  4. 4. Wait 15–30 seconds for the new session to be established

502 — Request Signing Failure

The internal signing service could not sign the request. This is typically a temporary infrastructure issue.

Steps to fix:

  1. 1. Wait a few seconds and retry the request
  2. 2. If the error persists for more than a few minutes, contact support

Signing errors are not billable

Requests that fail due to signing errors do not deduct any credits.

500 — INTERNAL_ERROR

An unexpected server-side error occurred.

Steps to fix:

  1. 1. Retry the request — most 500 errors are transient
  2. 2. If the error is consistent for a specific endpoint + model combination, contact support with the request details
PreviousModel SetupConnect a model step by stepNextChangelogWhat's new