# Testing in staging (/testing-in-staging)

The staging environment is a full copy of the e-Próspera portal where you can test your integration for free. All API endpoints, OAuth flows, and payment steps work identically to production.



## Base URLs [#base-urls]

| Environment | Base URL                               |
| ----------- | -------------------------------------- |
| Production  | `https://portal.eprospera.com`         |
| Staging     | `https://staging-portal.eprospera.com` |

## Getting access [#getting-access]

Email [gmembreno@prospera.hn](mailto:gmembreno@prospera.hn) with a brief description of what you're building. We'll provision:

* A staging account with an API key
* An OAuth client (if you need OAuth / OIDC)

## Making requests [#making-requests]

Everything works the same as production. With the CLI, set `EPROSPERA_ENV=staging`:

```bash
export EPROSPERA_API_KEY="<your-staging-api-key>"
EPROSPERA_ENV=staging eprospera --json entity verify 80000000000012
```

For direct HTTP, use the staging base URL:

```bash
curl -X POST https://staging-portal.eprospera.com/api/v1/verify_rpn \
  -H "Authorization: Bearer <your-staging-api-key>" \
  -H "Content-Type: application/json" \
  -d '{"rpn": "80000000000012"}'
```

See the [quickstart](/getting-started) for more details.

## OAuth in staging [#oauth-in-staging]

OAuth endpoints work identically to production at the staging base URL. See the [OAuth overview](/oauth-overview) for the full flow.

## Voucher codes for entity applications [#voucher-codes-for-entity-applications]

Entity applications [require payment via voucher](/reference/post-legal-entity-applications-id-pay-voucher). In production you purchase voucher codes from Próspera; on staging, use this code to incorporate as many entities as you need:

```text
API1234
```