Getting started
Sandbox
A hosted sandbox environment is on the roadmap. Today, every API call hits live infrastructure tied to your account.
Coming soon. A hosted sandbox with simulated PSTN and pre-seeded test data is on the roadmap but not yet available. Right now every request hits production infrastructure scoped to your account.
Today
There is no separate sandbox host. The Vinix Core API is the same endpoint surface whether you're prototyping or in production — auth tokens, callflows, devices, numbers, and CDRs all live in the same account.
Practical implications while sandbox is unavailable:
- Outbound PSTN traffic costs real money. Originate cautiously, or ring internal extensions only.
- Inbound numbers that you've claimed will ring real devices, so point them at a test callflow or a non-prod user during development.
- Webhooks fire against the URI you configure — point them at a staging service rather than production-facing endpoints.
What sandbox will offer
When the hosted sandbox ships, expect:
- A distinct base URL (
api-sandbox.vinixglobal.com), separate account ID, and separate API key — see Authentication. - Simulated PSTN — outbound calls progress through
CHANNEL_CREATE/CHANNEL_ANSWER/CHANNEL_DESTROYlifecycle without dialing real numbers, so call-flow and webhook integrations can be tested without spending trunk minutes. - Pre-seeded users, numbers, and a default callflow so a fresh sandbox account is immediately useful.
Reach out to [email protected] if you need early access — internal pre-production environments may be available case-by-case.