We've been API-first since 1996, before they were called APIs. The portal you log into is built on the same public API we give you, so anything you can click, you can automate: provision numbers, change routing, pull CDRs, send messages and drive AI - by hand or by code, in seconds.
Provision UK and US numbers, automate porting, change routing and pull CDRs. Wholesale termination, origination and SMS on the network we own. Wholesale API reference →
Stand up unscripted, goal-driven voice agents and feed them per-call context. Conversational AI docs →
Define your own Operators, receive the typed signals they emit by webhook, and query vCon memory in your own storage. Conversation Intelligence docs →
API-first since 1996 · one authenticated gateway · industry-standard SMPP for messaging
Generate a key in the Customer Portal. The full key is shown once, at creation - we keep only a hash and can't show it to you again, so store it securely. Each key carries a set of scopes that control what it can do.
Send it as a Bearer token in the Authorization header. Every service on the gateway lives behind the same host, versioned independently:
curl https://api.simwood.com/... \
-H "Authorization: Bearer YOUR_API_KEY"Services share the same authentication, versioning and error conventions, so once you've integrated one, the next is familiar. Start with Getting started and Authentication.
The full API reference lives at docs.simwood.com. One exception: Hosted PBX currently has its own API on a separate site, developer.simwood.com - not to be confused with the main docs - and is set to merge into the main API in due course.
Yes. Simwood has been API-first since 1996, and the customer portal is built on the same public API given to customers, so anything you can click you can automate. Full documentation is at docs.simwood.com.
Generate an API key in the Customer Portal at portal.simwood.com - the full key is shown once at creation and Simwood keeps only a hash, so store it securely - then send it as a Bearer token in the Authorization header. Each key carries a set of scopes that control what it can do.
Services sit behind a unified gateway at https://api.simwood.com, and each service is versioned independently so you can adopt new capabilities without breaking existing integrations. Each service's exact paths are in its reference documentation at docs.simwood.com.
Provision numbers, change routing and pull CDRs in seconds, automate porting, build client apps and intelligent routing, send SMS (industry-standard SMPP is supported), and drive Conversational AI and Conversation Intelligence - by hand in the portal or by code.
Not yet. Hosted PBX - and everything to do with it, including the portal, provisioning, billing and routing - currently runs on its own separate API, documented on a separate site at developer.simwood.com/docs/direct/introduction (not the main docs.simwood.com). It is set to merge into the main Simwood API in due course.
Yes. Services on the api.simwood.com gateway share the same authentication, versioning and error conventions, while each owns its own contract, so integrating a second service is familiar once you have integrated the first. See docs.simwood.com/conventions.
Yes. The Wholesale API v3 remains available and documented alongside the newer service-specific APIs for Conversational AI and Conversation Intelligence. All of it is documented at docs.simwood.com.
Same core, same API, same intelligence - whatever door you come in through.