Read the right account
Environment data should be scoped to the authorised customer, including extensions, numbers and routing.
Developer experience
Build around a clear event and a clear permission.
The planned developer interface covers customer environments, call history and event notifications. It is a development roadmap, not a connected public API.
Respond to an event
Planned webhook types include call started, call ended, missed call, voicemail received and invoice issued.
Avoid duplicate changes
Production writes need verified requests, replay protection and an auditable provisioning queue.
What to work through
Step 1
Define access
Agree the account and the minimum permissions required.
Step 2
Test with examples
Use sample payloads and an isolated environment before handling real records.
Step 3
Check the result
Track errors, retries and duplicate events before enabling production traffic.
Questions you might have
Where are the production keys?
This tool has no public API credentials or connected production API. The live developer portal is a separate CRM deliverable.
Can I export the studio design?
Yes. The JSON export uses schemaVersion 1 with nodes, branch-labelled edges and commercial selections. The same object drives this website simulator.
Put it into a design.
Add your teams, try the caller journey and download an itemised estimate from the builder.
Build your system