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

# Sandbox Environment

> Build in Sandbox, deploy in Production

hConnect provides two environments for development and deployment: **Sandbox** and **Production**. Both environments use the same API structure, so you can build once and deploy with confidence.

## Sandbox Environment

The Sandbox is designed for **testing and integration**.

* Use **sandbox credentials** to simulate identity verification.
* API responses and data formats are identical to Production.
* Ideal for development, QA, and staging environments.

<Warning>
  **Note:** Real eIDs are not supported in Sandbox. Any attempt to use live credentials will fail.
</Warning>

## Production Environment

The Production environment is for **live verification with real credentials**.

* Requires **production credentials** issued by Hopae.
* Verifications are performed against real-world eIDs.
* Behaves identically to Sandbox, so integration changes are not required.

<Info>
  To activate Production access, you must complete a **final solutioning call with the Hopae team**.\
  This ensures your integration is configured correctly, meets compliance requirements, and is ready for go-live.
</Info>

## Environment Comparison

| Feature              | **Sandbox**                     | **Production**                           |
| :------------------- | :------------------------------ | :--------------------------------------- |
| Purpose              | Testing & integration           | Live verification with real credentials  |
| Credentials          | Sandbox credentials (test only) | Production credentials (issued by Hopae) |
| Data                 | Simulated test data             | Real eID data                            |
| Availability of eIDs | New eIDs launched here first    | Announced in release notes after review  |
| Usage                | Development, QA, staging        | Live enterprise deployments              |
| Access Requirements  | Available to all developers     | Requires solutioning call + approval     |

## Recommended Workflow

1. **Start in Sandbox**
   * Integrate using test credentials.
   * Validate your workflows end-to-end.
2. **Request Production Access**
   * Schedule a solutioning call with Hopae.
   * Confirm compliance and readiness.
3. **Go Live**
   * Switch your API key from Sandbox to Production.
   * Both environments share the same API base URL. Only the **API Key** changes.

## FAQ

**Q: Can I use real eIDs in the Sandbox environment?**\
No. Sandbox only accepts test credentials. Any attempt to use real eIDs will fail.

**Q: How do I move from Sandbox to Production?**\
Complete your integration in Sandbox, then request a solutioning call with Hopae. After review, we’ll issue Production credentials.

**Q: Are the API responses different between Sandbox and Production?**\
No. The API structure and responses are identical. The only difference is that Sandbox returns simulated data, while Production returns real data.

**Q: Why is the solutioning call required before Production access?**\
The solutioning call ensures your integration is configured correctly, meets compliance requirements, and can handle real-world usage without issues.

**Q: How are new eIDs released?**\
All new eIDs are first introduced in Sandbox. After validation, they are promoted to Production, with release notes announcing availability.

**Q: Can I test edge cases and errors in Sandbox?**\
Yes. The Sandbox environment is designed to let you test success and error scenarios safely. Refer to the documentation for error simulation options.