AntifraudAI API Rate Limits: Quotas, Headers & 429 Handling

AntifraudAI enforces rate limits on a per-API-key basis using a sliding one-minute window. Rate limits exist to ensure fair resource allocation across all customers and to protect the reliability of the platform. If you exceed your limit, requests will be rejected with a 429 Too Many Requests response until the window resets.

Default Rate Limits

Environment	Limit
Sandbox	100 requests / minute
Production (Starter)	1,000 requests / minute
Production (Growth)	5,000 requests / minute
Production (Enterprise)	Custom

Rate limits apply per API key, not per IP address. If you use multiple keys for different services, each key has its own independent quota.

Rate Limit Headers

Every API response — including error responses — includes the following headers so you can monitor your usage in real time:

Header	Description
`X-RateLimit-Limit`	The maximum number of requests allowed in the current window
`X-RateLimit-Remaining`	The number of requests remaining in the current window
`X-RateLimit-Reset`	Unix timestamp (seconds) at which the current window resets

Example response headers:

X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 843
X-RateLimit-Reset: 1718445720

Check X-RateLimit-Remaining before each burst of requests. If it drops below a safe threshold (e.g., 50), introduce a short delay in your sending loop to avoid hitting the limit and triggering retries.

Handling 429 Errors

When the rate limit is exceeded, the API returns a 429 Too Many Requests response:

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "You have exceeded your rate limit of 1000 requests per minute. Please retry after the window resets."
  }
}

The response will also include a Retry-After header indicating how many seconds to wait before retrying. The recommended strategy is exponential backoff with jitter — wait an increasing amount of time between retries, with a small random offset to prevent synchronized retry storms across multiple workers.

import time
import random
import requests

def screen_transaction(payload, api_key, max_retries=5):
    url = "https://api.antifraudai.com/v1/transactions/screen"
    headers = {
        "Authorization": f"Bearer {api_key}",
        "Content-Type": "application/json",
    }

    for attempt in range(max_retries):
        response = requests.post(url, headers=headers, json=payload)

        if response.status_code != 429:
            return response.json()

        # Exponential backoff with full jitter
        base_delay = 2 ** attempt          # 1s, 2s, 4s, 8s, 16s
        jitter = random.uniform(0, base_delay)
        wait = base_delay + jitter

        retry_after = int(response.headers.get("Retry-After", wait))
        sleep_time = max(retry_after, wait)

        print(f"Rate limited. Retrying in {sleep_time:.2f}s (attempt {attempt + 1}/{max_retries})")
        time.sleep(sleep_time)

    raise Exception("Max retries exceeded after repeated 429 responses.")

async function screenTransaction(payload, apiKey, maxRetries = 5) {
  const url = "https://api.antifraudai.com/v1/transactions/screen";
  const headers = {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  };

  for (let attempt = 0; attempt < maxRetries; attempt++) {
    const response = await fetch(url, {
      method: "POST",
      headers,
      body: JSON.stringify(payload),
    });

    if (response.status !== 429) {
      return response.json();
    }

    // Exponential backoff with full jitter
    const baseDelay = Math.pow(2, attempt) * 1000; // ms
    const jitter = Math.random() * baseDelay;
    const retryAfter = parseInt(response.headers.get("Retry-After") ?? "0") * 1000;
    const sleepTime = Math.max(retryAfter, baseDelay + jitter);

    console.log(`Rate limited. Retrying in ${(sleepTime / 1000).toFixed(2)}s (attempt ${attempt + 1}/${maxRetries})`);
    await new Promise((resolve) => setTimeout(resolve, sleepTime));
  }

  throw new Error("Max retries exceeded after repeated 429 responses.");
}

Do not retry immediately on a 429 response. Tight retry loops without backoff will keep triggering the rate limit and may result in your key being temporarily suspended.

Overview

Endpoints

AntifraudAI API Rate Limits: Quotas, Headers & 429 Handling

Default Rate Limits

Rate Limit Headers

Handling 429 Errors

​Default Rate Limits

​Rate Limit Headers

​Handling 429 Errors

Default Rate Limits

Rate Limit Headers

Handling 429 Errors