How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Speko Voice API

The Voice API from Speko — 8 operation(s) for voice.

Speko Voice API is one of 4 APIs that Speko publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Voice. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 9 operations across 8 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.speko.dev.

9 operations 8 paths 19 schemas 4 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.speko.dev
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Speko Voice API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API key (sk_live_...)) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 9

Across 8 paths, the API surfaces 9 operations — 4 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Voice 9
POST
/v1/sessions
Create a real-time voice session
createSession body → 201400401500
GET
/v1/sessions
List voice sessions
listSessions 5 params → 200401
POST
/v1/transcribe
Transcribe audio (speech to text)
transcribe 4 params body → 200400401500
GET
/v1/voices
List TTS voices
listVoices 1 param → 200401
POST
/v1/synthesize
Synthesize speech (text to speech)
synthesize body → 200400401500
POST
/v1/complete
Generate an LLM completion
complete body → 200400401500
GET
/v1/sessions/{id}/recording
Get a signed URL for the session recording
getSessionRecording 1 param → 302401404
POST
/v1/sessions/{id}/turns
Ingest finalized transcript turns
postSessionTurns 1 param body → 202400401404
GET
/v1/sessions/{id}/transcript
Get a session's full transcript
getSessionTranscript 1 param → 200401404

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are CompleteRequest (11 properties), CreateSessionRequest (10 properties), TurnEntry (8 properties), SessionEntry (8 properties). Each schema is shown below with its type and property counts.

SessionEntries
object
2 properties 1 required
ChatTool
object
5 properties 3 required
PostSessionTurnsRequest
object
1 property 1 required
SessionEntry
object
8 properties 2 required
PipelineConstraints
object
1 property
VoiceCatalogEntry
object
3 properties 3 required
SessionTranscript
object
1 property 1 required
ChatMessage
object
5 properties 2 required
TurnEntry
object
8 properties 5 required
VoicesProviderEntry
object
4 properties 4 required
SynthesizeRequest
object
6 properties 2 required
Error
object
2 properties 2 required
TurnIngest
object
7 properties 4 required
RoutingIntent
object
3 properties 1 required
CompleteRequest
object
11 properties 2 required
CreateSessionRequest
object
Cascade-mode session creation body. Exactly one of agentId or intent must be supplied. When agentId is given, the persisted agent's systemPrompt, voice, intent…
10 properties
ChatToolCall
object
3 properties 3 required
CreateSessionResponse
object
8 properties 8 required
VoicesListResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

speko-voice-api-openapi.yml Raw ↑

Other APIs Speko publishes across the network.

Speko Agents API
Speko Providers API
Speko Telephony API
Where this information came from

This is an independent, third-party profile of Speko Voice API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.