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

# Test helpers

> Use Uphold Sandbox-only test helpers to simulate deposits, withdrawals, and compliance state changes — speeding up integration testing without real events.

Test helpers are specialized endpoints designed to help you simulate various external events, scenarios, and states within the **Sandbox environment**, such as receiving deposits, handling withdrawals, or triggering compliance statuses.

<Warning>Test helpers are only available in the Sandbox environment and will return `404 Not Found` if called in Production.</Warning>

## Why use test helpers?

During development and testing, you often need to simulate external events that would normally be triggered by third-party systems or real-world actions. To simplify these simulations, test helpers enable you to:

<CardGroup cols={2}>
  <Card title="Simulate specific events" icon="play">
    Quickly and reliably simulate events without waiting for real-world processes (e.g., an incoming bank deposit).
  </Card>

  <Card title="Test edge cases" icon="triangle-exclamation">
    Test edge cases and failure scenarios like account opening rejection and user sanctioned.
  </Card>

  <Card title="Integration testing" icon="code">
    Validate your application's integration with the APIs in a controlled environment.
  </Card>

  <Card title="Automated testing" icon="robot">
    Build comprehensive automated test suites with predictable external event simulation.
  </Card>

  <Card title="Event validation" icon="circle-check">
    Verify your handling of specific event-driven behaviors and webhook notifications.
  </Card>

  <Card title="Pre-production prep" icon="rocket">
    Prepare and validate your implementation before moving to Production.
  </Card>
</CardGroup>

## Key concepts

* **Event triggering:** API-driven activation of events to simulate real-world scenarios.
* **Asynchronous behavior:** Many test helpers return a `202 Accepted` status, indicating that the request has been accepted and processing is asynchronous.
* **Resource management:** Automatically create or modify resources in response to simulated external events.

<Note>
  Before using test helpers, keep the following considerations in mind:

  * Behavior in Sandbox may differ slightly from Production in terms of performance, response times, and event handling.
  * Ensure your integration code is environment-aware to prevent accidental calls to Sandbox endpoints from Production environments.
</Note>

Explore the detailed documentation for each test helper to start simulating events and scenarios, streamlining your testing and integration workflow.

<Info>You can find these endpoints within the **Test helpers** folder, located under each API's group of endpoints in the API documentation.</Info>