Sandbox Testing

Use sandbox to validate integration behavior before you switch to live.

Use sandbox to test:

• API key handling
• webhook signature verification
• receiver idempotency
• subscription matching
• delivery logs and replay behavior
• event-feed reconciliation

What sandbox gives you

Sandbox lets you:

• create sandbox API keys
• review webhook endpoints for your test receiver
• create or review subscription rules
• send manual webhook pings
• generate synthetic subscription-scoped test events

Synthetic sandbox events are tagged as test events:

• source_kind = "sandbox_event"
• data.sandbox_event.is_test = true

Validate webhook delivery

1. create or review a webhook endpoint that points at your test receiver
2. send a manual ping first
3. create or review the subscription rule you want to validate
4. use Generate test on that rule in the portal
5. inspect the delivery attempt in the portal

Use delivery history to verify:

• headers and signature
• request body shape
• source metadata
• failure category and latency
• replay and redelivery behavior

Validate event-feed reconciliation

For reconciliation reads:

1. create a sandbox API key
2. create or review a subscription rule in the portal
3. generate a sandbox test event for that rule
4. read /v1/events or an issuer/fund-scoped feed

Example:

curl -s "https://sandbox-api.rangler.co/v1/events?limit=10" \
  -H "X-API-Key: atl_test_your_key_here" | python3 -m json.tool

Look for:

• source_kind = "sandbox_event"
• your expected event_type
• the relevant company_id or fund_id

Which synthetic events are supported today

Atlas currently supports sandbox generation for:

• filing.new
• fund.disclosure.updated

The available choice depends on the rule’s current event types and scope.

Recommended workflow

Use sandbox in this order:

1. Ping your receiver to confirm transport and signature verification
2. Generate test events to validate subscription matching
3. Read event feeds as a reconciliation path after webhook validation

Important boundaries

• Sandbox and live should use separate API keys and distinct receiver URLs or endpoint configs in your own systems
• Treat sandbox events as integration fixtures, not market truth
• Keep event-feed reconciliation available after you enable webhooks in production

See Quickstart, Webhooks and Event Feeds, and Webhooks for the surrounding integration contract.