Skip to main content

Environments

Each MAES Platform project has two completely isolated environments: Sandbox and Production.

Sandbox Environment​

The sandbox is your development playground.

Characteristics​

  • ✅ Mock data — No real MAES operations
  • ✅ Safe testing — Experiment without consequences
  • ✅ Instant responses — No waiting for MAES portal
  • ✅ Webhook testing — Event simulator & scheduled events

Use Cases​

  • Developing new integrations
  • Testing edge cases
  • CI/CD pipelines
  • Demo environments

API Key Prefix​

sk_sandbox_aBcDeFgHiJkLmNoPqRsTuVwXyZ...

Production Environment​

Production connects to the real MAES portal.

Characteristics​

  • ⚡ Real operations — Actual MAES portal changes
  • 🔄 Background sync — Data synced from MAES
  • 📊 Live data — Real card information
  • 🔔 Real events — Actual webhook notifications

Use Cases​

  • Live fleet management
  • Real card operations
  • Production integrations

API Key Prefix​

sk_live_aBcDeFgHiJkLmNoPqRsTuVwXyZ...

Environment Isolation​

Environments are completely isolated:

AspectSandboxProduction
CardsMock/test cardsReal MAES cards
API Keyssk_sandbox_*sk_live_*
WebhooksIndependent configIndependent config
OperationsInstant (simulated)Background (real)
warning

You cannot access production data with a sandbox API key, and vice versa.

Switching Environments​

In the Dashboard​

Click the environment tab in your project:

[Project Name]
├── 🧪 Sandbox    ← Click to switch
└── 🚀 Production ← Click to switch

In Your Code​

Simply use the appropriate API key:

// Development/Testing
const API_KEY = process.env.MAES_SANDBOX_KEY; // sk_sandbox_...

// Production
const API_KEY = process.env.MAES_PRODUCTION_KEY; // sk_live_...

Sandbox-Only Features​

These features are available only in sandbox:

Event Simulator​

Manually trigger webhook events for testing:

POST /projects/{id}/webhook/simulate
{
  "event": "card.enabled",
  "cardId": "optional-card-uuid"
}

Scheduled Events​

Automatically send test events at intervals:

PATCH /projects/{id}/webhook/scheduler
{
  "enabled": true,
  "intervalHours": 6,
  "scheduledEvents": ["card.enabled", "card.disabled"]
}

Best Practices​

  1. Always develop in sandbox first
  2. Use environment variables for keys
  3. Test all edge cases in sandbox
  4. Have separate CI/CD keys
  5. Monitor production separately
# .env.development
MAES_API_KEY=sk_sandbox_xxxxx

# .env.production
MAES_API_KEY=sk_live_xxxxx