Move from Sandbox to Live
Move to Live only after Sandbox tests pass and Voyced has enabled Live access for your integration.
Your API credentials can access customer information and the functions allowed for that key. Treat the API secret like a password. Store it only in protected server-side settings or a trusted secret store.
- Never put an API key, API secret or bearer token in public code, browser JavaScript, screenshots, URLs or support messages.
- Keep Sandbox and Live credentials separate. Give each integration only the permissions it needs.
- Rotate the secret and disable the old key at once when exposure is suspected.
Sandbox
https://sandbox.voycedconnect.eu/v1
Build and check your integration without using Live credentials.
Live
https://api.voycedconnect.eu/v1
Use only after your tests pass and Voyced has enabled Live access.
Change exactly these values
Base URL
Change Sandbox to https://api.voycedconnect.eu/v1.
API key and secret
Replace both Sandbox values with the separate Live values supplied by Voyced.
Bearer token
Request a new token from Live. Never copy a Sandbox token.
What changes
| Setting | Sandbox | Live |
|---|---|---|
| Base URL | https://sandbox.voycedconnect.eu/v1 | https://api.voycedconnect.eu/v1 |
| API key | Sandbox key | Separate Live key supplied by Voyced |
| API secret | Sandbox secret | Separate Live secret supplied by Voyced |
| Bearer token | Requested from Sandbox | Request a new token from Live |
| Permissions | Sandbox permissions | May differ. Check capabilities again. |
| Data | Sandbox access | Live customer information |
What stays the same
- The
/v1path - Endpoint paths
- Request and response formats
- Bearer-token header format
- Error structure and request IDs
Use environment settings
Do not hard-code the URL or credentials. Keep Sandbox and Live settings separate.
# Sandbox
VOYCED_API_BASE_URL=https://sandbox.voycedconnect.eu/v1
VOYCED_API_KEY=YOUR_SANDBOX_API_KEY
VOYCED_API_SECRET=YOUR_SANDBOX_API_SECRET
# Live, use only after approval
VOYCED_API_BASE_URL=https://api.voycedconnect.eu/v1
VOYCED_API_KEY=YOUR_LIVE_API_KEY
VOYCED_API_SECRET=YOUR_LIVE_API_SECRETGo-live process
Complete Sandbox testing
Test the full workflow, including failures, retries and token renewal.
Request Live access from Voyced
Provide the integration purpose, required permissions and expected request volume.
Store the Live credentials separately
Never overwrite or copy Sandbox credentials into the Live configuration.
Request a Live bearer token
Use the Live key and secret with https://api.voycedconnect.eu/v1/auth/token.
Run Live checks
Run the connection test and capabilities endpoint before enabling the complete workflow.
Start with controlled traffic
Watch API responses, request IDs, rate limits and the Voyced status page.
First Live smoke tests
After you receive a Live bearer token, run these two read-only checks before starting the full workflow.
curl --request GET \
--url 'https://api.voycedconnect.eu/v1/test' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer YOUR_LIVE_BEARER_TOKEN'curl --request GET \
--url 'https://api.voycedconnect.eu/v1/capabilities' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer YOUR_LIVE_BEARER_TOKEN'- Keep the tested Sandbox setup unchanged.
- Enable Live for a small, controlled test first.
- Check the Live request IDs, responses and workflow logs.
- Increase normal traffic only after the smoke tests pass.
- When a Live test fails, stop the Live workflow and return to the unchanged Sandbox copy while you correct it.
Safe activation and rollback
Do not enable scheduled jobs or high request volumes until both checks succeed and the required Live permissions are available.