Docs

Sandbox environment

Free, isolated environment for development and CI. Synthetic data, no billing, no impact on production keys.

What sandbox keys do

Sandbox keys (prefix ck_sbox_) hit a fully isolated copy of CLEARIE™ GETWAY backed by a separate database schema seeded with synthetic, deterministic data. Real customer records never appear in sandbox responses.

Use sandbox for local development, integration tests, and CI pipelines. No quota draws from your paid plan, no AI credits are billed.

Quotas

100 calls per rolling 7-day window per sandbox key.

2 requests/second burst.

25 sandbox AI credits per week (returns canned analyses).

1-day log retention.

Base URL & switching

Sandbox shares the same base URL as production; the key prefix routes the request to the correct environment.

# Sandbox
  curl --oauth2-bearer "$CLEARIE_SANDBOX_API_KEY" \
     https://getway.clearie.ai/v1/master/hsn/exports?code=2710

# Production
  curl --oauth2-bearer "$CLEARIE_PRODUCTION_API_KEY" \
     https://getway.clearie.ai/v1/master/hsn/exports?code=2710

Determinism

Identical sandbox requests always return identical bodies (modulo timestamps). Snapshot-test against sandbox responses without flakiness.

What sandbox does NOT include

Sandbox uses reduced reference datasets and sandbox-only API keys. It does not provide production traffic guarantees, multi-region failover certification, or on-premises connector simulation. Outbound webhook delivery is available for configured HTTPS test endpoints.