Numbers
GET /api/v1/numbersList the numbers assigned to your account. Inspect an individual number and use supported updates to its label and incoming or failure call behaviour.
SAYVONA FOR DEVELOPERS / VOICE APIYour next idea
Your next idea
has a voice.
Connect your application to business numbers, SIP endpoints and programmable call flows. Start with a guided integration pilot. Confirm supported operations, runtime and carrier costs before production. Embedded SDK access is a planned capability.
START WITH THE BUILDING BLOCKSA number.
A number.
Some logic.
Your possibilities.
Work with the numbers assigned to your account using a scoped API key. Use the API base URL supplied during onboarding, and keep credentials on your server.
// Start with a number. Make it yours.
const response = await fetch(
`${baseUrl}/api/v1/numbers`,
{ headers: { "X-API-Key": apiKey } }
);
const numbers = await response.json();GET/api/v1/numbersapplication/json
Use the API base URL and scoped key supplied with your account.
FREE ACCESS. CLEAR USAGE COSTS.Build without
Build without
a seat licence
in the way.
You do not need contact-centre seats simply to explore a supported API integration. Standard API access has no separate access fee. Production capabilities, processing, capacity and support are scoped in the pilot quote.
The REST API is the integration starting point today. The Sayvona SDK is planned; production embedding rights, supported clients and release availability must be confirmed before building around it.
Rent numbers when you need them. Pay for incoming and outgoing telephone usage on Sayvona’s connection. Live call flows running on Sayvona have a separately agreed runtime price with either carrier. Media streaming, recording and managed AI are identified in your quote, including anything bundled in a package.
Estimate developer calling costsTHE API SURFACEUseful primitives.
Useful primitives.
Familiar requests.
Availability depends on your enabled account capabilities and API-key scopes. We walk through the relevant request and response shapes during integration.
SIP endpoints
GET /api/v1/endpointsList and manage compatible endpoints through the supported create, update and delete operations. Connect the account to the PBX or SIP destination your flow needs.
Calling policies
GET /api/v1/calling-policiesRead the outbound calling policies available to your account. Confirm allowed destinations and the applicable calling configuration before sending traffic.
MAKE VOICE PART OF THE PRODUCTYour application.
Your application.
A real connection.
Numbers with application logic.
Use a number as the entry point to a supported call flow. Configure the destination, greeting and failure path around the experience you want to deliver.
Existing telephone infrastructure.
Connect compatible SIP endpoints and discuss a customer-supplied trunk. Agree the media path, authentication and caller-ID behaviour for the deployment.
An AI calling experience.
Bring a concrete voice-AI use case to the integration discussion. Separate the telephone connection from your model, speech and media-processing needs.
Account-aware integrations.
Use the key scopes and resource boundaries supplied for your account. Design your application to handle denied requests, unavailable destinations and retries.
BUILDING WITH VOICE AIScope the
Scope the
whole conversation.
An AI-only application still consumes telephony or processing resources. Your price should reflect the services in the call path.
You bring the AI.
Keep your preferred AI provider and agree how it connects to the call. You pay your provider directly. Sayvona charges for its live call processing and any supplied numbers, calling or media service. Using your own carrier and AI provider still leaves the Sayvona runtime to be priced.
We confirm supported transport, audio format, concurrency and media-service costs before committing to the integration.
We provide managed AI.
Let us scope the speech and AI configuration with you. Processing is priced separately from the incoming or outgoing telephone leg, including when the carrier is yours.
A pilot establishes the supported workflow, usage limits, handover and commercial scope before wider deployment.
See the AI receptionist use caseDEVELOPER & SIP USAGE PRICINGStart simply.
Start simply.
Grow on
clear terms.
Choose how you buy telephone usage. These arrangements sit alongside your numbers and any software or managed services you need.
Flexible from the first call.
Pay for the Sayvona call processing you use, plus any numbers and telephone airtime we supply. Standard API access carries no separate access fee.
For pilots and changing trafficStart with usagePlan around predictable traffic.
Share your expected monthly usage and destinations. We can model a committed rate and support arrangement when the volume justifies it.
For established production trafficDiscuss volume pricingBuild around your operation.
Discuss larger traffic volumes, multiple environments, additional capacity and scoped integrations. Agree the deployment and service responsibilities together.
For larger or specialised deploymentsTalk to salesCommitted and Enterprise quotes account for destinations, traffic, simultaneous calls, hosting and support. Numbers, telephone usage, live call processing, hosted media and managed AI remain separately identified. Bringing your carrier does not remove the charge for runtime supplied by Sayvona. Any minimum spend or commitment period is agreed in the quote.
See the number and calling rate cardA CLEAR WAY TO GET STARTEDFrom idea to
From idea to
“hello, world.”
01 /
Describe the call journey.
Tell us what triggers a call, who talks, where audio goes and what happens if the application cannot respond. Include expected traffic and destinations.
02 /
Connect your account.
Agree number or trunk supply, receive your API base URL and scoped credentials, and check the supported operations using a small integration.
03 /
Verify and launch.
Check audio, callbacks, authentication and failure paths. Confirm tariffs, billing increments, concurrency and any managed-service charges before live traffic.
Is API access really free?+
Standard API access has no separate access fee. Production call processing, hosted media and supported capabilities are agreed separately. A future embedded SDK may be included in a software edition or have its own licence; production SDK access is not generally available.
Do I need to buy contact-centre seats?+
No. An application can use the developer offer without an agent plan. If you also need human agents working from the contact-centre interface, those users require an appropriate plan.
What if all my calls are incoming?+
Incoming calls on the displayed local Sayvona number offer cost KES 1.00/minute, plus number rental. Hosted call processing still has its own agreed price. Managed AI voice agents are KES 3,000 a month each plus KES 10–14 a minute (premium voices from KES 25); additional media services, if used, are separately scoped. There is no dependency on your application generating outbound traffic.
What if I bring both my carrier and my AI provider?+
You pay those providers for their services. Sayvona’s live call processing remains a paid service. Standard API access does not include runtime, hosted media or managed infrastructure. SDK production terms are to be confirmed. If everything runs outside Sayvona, there is no Sayvona-hosted call usage to charge for.
Can I put my API key in a browser or mobile app?+
Keep account API keys on a trusted server. They authorise account resources and should not be embedded in a public client. We confirm the appropriate access pattern for your application during onboarding.
Where can I get an SDK?+
There is no generally available Sayvona SDK release today. Start with the supported REST API pilot and discuss your embedded calling requirements. The Voice SDK page explains the planned capability and production access considerations.
LET’S MAKE THE CONNECTION
We’d love to hear what you’re building.
Bring your questions. Let’s work through your setup.