> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rangler.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Sandbox Testing

> Validate Rangler API keys and webhook receivers with managed test deliveries before going live.

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

Use sandbox to test:

* API key handling
* webhook signature verification
* receiver duplicate-delivery protection
* delivery logs and replay behavior
* checks for missed events through the event feed

## What sandbox gives you

Sandbox lets you:

* create sandbox API keys
* review webhook endpoints for your test receiver
* create or review market-event subscription rules
* send managed test events to a selected endpoint
* inspect and redeliver managed delivery attempts

Managed test deliveries are tagged in their data:

* `data.sandbox = true`
* `data.generated_by = "rangler_portal"`

## Validate webhook delivery

1. create or review a webhook endpoint that points at your test receiver
2. use **Send test event** for that endpoint
3. select `filing.new` or `fund.disclosure.updated`
4. inspect the queued 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

## Check event-feed recovery separately

When checking for missed events:

1. create a sandbox API key
2. read `/v1/events` or an issuer/fund-scoped feed

Example:

```bash theme={null}
curl -s "https://sandbox-api.rangler.co/v1/events?limit=10" \
  -H "X-API-Key: rgl_test_your_key_here" | python3 -m json.tool
```

Managed endpoint test events are not inserted into these feeds. Use feed reads to validate authentication, filters, page tokens, and missed-event handling against sandbox data separately from webhook delivery testing.

## Which synthetic events are supported today

Rangler currently supports sandbox generation for:

* `filing.new`
* `fund.disclosure.updated`

These choices test the endpoint directly and do not depend on a subscription rule.

## Recommended workflow

Use sandbox in this order:

1. **Send a managed test event** to confirm transport and signature verification
2. **Inspect delivery history** and redeliver failures after fixing the receiver
3. **Read event feeds** to validate earlier-record loading and missed-event handling separately

## 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 a scheduled event-feed check after you enable webhooks in production

See [Quickstart](/quickstart), [Webhooks and Event Feeds](/polling-vs-webhooks), and [Webhooks](/webhooks) for the surrounding integration contract.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.