Sandbox and Production Environments in AntifraudAI

AntifraudAI offers two isolated environments to serve different stages of your integration lifecycle. The sandbox environment gives you a safe, free space to build and test without affecting real user data. The production environment runs live fraud screening against real events and real users.

Environment Overview

	Sandbox	Production
Purpose	Development and testing	Live fraud screening
Base URL	`https://sandbox.antifraudai.com/v1`	`https://api.antifraudai.com/v1`
API Key Prefix	`sk_test_`	`sk_live_`
Data isolation	Fully isolated	Live user data
Billing	Free	Metered per event
Rate limits	100 req/min	1,000 req/min (default)

Creating Environment Keys

You can generate API keys for each environment directly from the AntifraudAI dashboard. Sandbox key

Log in to the AntifraudAI dashboard.
Navigate to Settings → API Keys.
Click Create Key under the Sandbox section.
Copy and securely store the generated sk_test_ key — it will not be shown again.

Production key

From the same Settings → API Keys page, switch to the Production section.
Click Create Key.
Copy and securely store the generated sk_live_ key.

Production keys are only available after your account has been activated. Complete onboarding in the dashboard before generating live keys.

Switching Environments

Switching between environments requires only two changes: the base URL and the API key. All request shapes, response schemas, and endpoint paths are identical across environments.

import os
import requests

# Set ANTIFRAUD_ENV=sandbox or ANTIFRAUD_ENV=production
env = os.getenv("ANTIFRAUD_ENV", "sandbox")

config = {
    "sandbox": {
        "base_url": "https://sandbox.antifraudai.com/v1",
        "api_key": os.getenv("ANTIFRAUD_SANDBOX_KEY"),
    },
    "production": {
        "base_url": "https://api.antifraudai.com/v1",
        "api_key": os.getenv("ANTIFRAUD_PRODUCTION_KEY"),
    },
}

base_url = config[env]["base_url"]
api_key = config[env]["api_key"]

response = requests.post(
    f"{base_url}/events/screen",
    headers={"Authorization": f"Bearer {api_key}"},
    json={"user_id": "usr_123", "amount": 79.99},
)
print(response.json())

const env = process.env.ANTIFRAUD_ENV || "sandbox";

const config = {
  sandbox: {
    baseUrl: "https://sandbox.antifraudai.com/v1",
    apiKey: process.env.ANTIFRAUD_SANDBOX_KEY,
  },
  production: {
    baseUrl: "https://api.antifraudai.com/v1",
    apiKey: process.env.ANTIFRAUD_PRODUCTION_KEY,
  },
};

const { baseUrl, apiKey } = config[env];

const response = await fetch(`${baseUrl}/events/screen`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ user_id: "usr_123", amount: 79.99 }),
});

const data = await response.json();
console.log(data);

Best Practices

Always test in sandbox first. Validate your integration end-to-end — including error handling and edge cases — before pointing your application at the production environment.

Use separate key storage per environment. Store sandbox keys in .env.development and production keys in .env.production (or your secrets manager). Never load both key sets at the same time in a running process.

Never mix sandbox and production data. Sandbox uses synthetic data that does not reflect real-world fraud patterns. Sending real user PII to the sandbox endpoint — or test IDs to production — will corrupt your analytics and may have compliance implications.

Rotate production keys regularly. Treat sk_live_ keys like passwords. Rotate them on a schedule or immediately after any suspected exposure. Old keys can be revoked instantly from the dashboard without downtime.

Get Started

Core Concepts

Guides

Configuration

Help

Sandbox and Production Environments in AntifraudAI

Environment Overview

Creating Environment Keys

Switching Environments

Best Practices

​Environment Overview

​Creating Environment Keys

​Switching Environments

​Best Practices

Environment Overview

Creating Environment Keys

Switching Environments

Best Practices