Quickstart: choose the right base URL — sandbox

2 min read

2 hostsSandbox mirror + production

1 varSwitch with a single env value

same pathsIdentical routes on both

The two hosts

Production — https://api.credicorp.co.uk. Real product data, real enquiries, production rate limits.
Sandbox — https://sandbox.credicorp.co.uk. A deterministic mirror with test data, looser limits and no side effects; safe to hammer in CI.

Both expose the identical /public/v1 route tree, so the only difference between environments is the host.

Drive it from one variable

# .env.development
CREDICORP_BASE=https://sandbox.credicorp.co.uk/public/v1

# .env.production
CREDICORP_BASE=https://api.credicorp.co.uk/public/v1

Read CREDICORP_BASE everywhere and you will never accidentally submit a test enquiry to production, or fail a CI run against live rate limits.

Fail safe by default

When the variable is unset, default to the sandbox host, not production. A missing config should degrade to the harmless environment, so a misconfigured deploy cannot silently write to your live enquiry stream.

Frequently asked questions

Are the endpoints identical on both hosts?

Yes. The sandbox mirrors the public ring route-for-route so you can develop against it and promote to production by changing only the host.

Is sandbox data stable?

Sandbox returns deterministic fixtures, so the same request gives the same response — ideal for snapshot tests and CI assertions.

Do I need separate keys per environment?

The public ring needs no keys at all. The partner ring uses separate OAuth2 client credentials per environment; never reuse production credentials in the sandbox.