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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Speko

Speko Telephony API

The Telephony API from Speko — 22 operation(s) for telephony.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 25 operations across 22 paths, and defines 39 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.

25 operations 22 paths 39 schemas 1 DELETE11 GET1 PATCH11 POST1 PUT

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
Contact
abat@speko.ai
Resource Areas
1

Authentication & Security 1

Speko Telephony 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 25

Across 22 paths, the API surfaces 25 operations — 1 DELETE, 11 GET, 1 PATCH, 11 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Telephony 25
POST
/v1/sessions/phone
Place an outbound phone call
createPhoneSession body → 200400401404
GET
/v1/agents/{id}/calls
List calls for an agent
listAgentCalls 4 params → 200401404
GET
/v1/phone-numbers
List phone numbers
listPhoneNumbers → 200401
POST
/v1/phone-numbers
Buy a managed phone number
createPhoneNumber body → 200400401
GET
/v1/phone-numbers/available
Search available managed numbers
searchAvailablePhoneNumbers 3 params → 200401
POST
/v1/phone-numbers/import
Import a SIP trunk phone number
importSipTrunkPhoneNumber body → 200400401
GET
/v1/phone-numbers/kyb
Get phone-number business verification
getPhoneNumberKyb → 200401
PUT
/v1/phone-numbers/kyb/draft
Save phone-number business verification draft
savePhoneNumberKybDraft body → 200400401
POST
/v1/phone-numbers/kyb/submit
Submit phone-number business verification
submitPhoneNumberKyb body → 200400401
GET
/v1/phone-numbers/{id}
Get a phone number
getPhoneNumber 1 param → 200401
PATCH
/v1/phone-numbers/{id}
Update a phone number
updatePhoneNumber 1 param body → 200400401
DELETE
/v1/phone-numbers/{id}
Release a phone number
deletePhoneNumber 1 param → 200401
GET
/v1/calls/{id}
Get call detail
getCall 1 param → 200401
GET
/v1/calls/{id}/events
List call events
listCallEvents 1 param → 200401
GET
/v1/calls/{id}/report
Get call report
getCallReport 1 param → 200401
POST
/v1/calls/{id}/report/finalize
Finalize call report
finalizeCallReport 1 param body → 200401
GET
/v1/calls/{id}/recording
Get call recording URL
getCallRecording 1 param → 200401
POST
/v1/calls/{id}/transfers/blind
Start blind transfer
blindTransferCall 1 param body → 201401
POST
/v1/calls/{id}/transfers/warm
Start warm transfer
warmTransferCall 1 param body → 201401
POST
/v1/calls/{id}/transfers/{transferId}/complete
Complete warm transfer
completeWarmTransfer 2 params body → 200401
POST
/v1/calls/{id}/transfers/{transferId}/cancel
Cancel warm transfer
cancelWarmTransfer 2 params body → 200401
GET
/v1/callbacks
List scheduled callbacks
listScheduledCallbacks 3 params → 200401
GET
/v1/callbacks/{id}
Get scheduled callback
getScheduledCallback 1 param → 200401
POST
/v1/callbacks/{id}/cancel
Cancel scheduled callback
cancelScheduledCallback 1 param body → 200401
POST
/v1/callbacks/{id}/dispatch
Dispatch scheduled callback now
dispatchScheduledCallback 1 param → 200401

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are PhoneNumber (23 properties), CallDetail (21 properties), ScheduledCallback (21 properties), CallTransfer (18 properties). Each schema is shown below with its type and property counts.

PhoneNumberSetupStatus
object
7 properties 7 required
AgentCallListEntry
object
12 properties 7 required
PipelineConstraints
object
1 property
PhoneNumberKybAuthorizedRepresentative
object
4 properties 3 required
FinalizeCallReportResponse
object
5 properties 5 required
PhoneNumberKybBusinessProfile
object
9 properties 8 required
PhoneNumberDirection
string
ScheduledCallbackStatus
string
PhoneNumberKybDraftRequest
object
3 properties 2 required
CallTranscriptEntry
object
9 properties 6 required
VoiceDialResponse
object
6 properties 6 required
ScheduledCallbacksResponse
object
1 property 1 required
E164
string
BlindTransferRequest
object
5 properties 1 required
TelephonyOptions
object
2 properties
CallEventsResponse
object
1 property 1 required
PhoneNumberKybOverview
object
3 properties 3 required
WarmTransferRequest
object
12 properties
JsonObject
object
CallDetail
object
21 properties 7 required
PhoneNumber
object
23 properties 8 required
PhoneNumberCreateRequest
object
5 properties 1 required
PhoneNumberKybSubmission
object
14 properties 6 required
CallEvent
object
12 properties 7 required
PhoneNumberKybSubmitRequest
PhoneNumberUpdateRequest
object
4 properties
Error
object
2 properties 2 required
RoutingIntent
object
3 properties 1 required
CallReport
object
14 properties 5 required
AvailablePhoneNumber
object
6 properties 6 required
CallTransferResponse
FinalizeCallReportRequest
object
2 properties
VoiceDialRequest
object
13 properties 1 required
CompleteWarmTransferRequest
object
2 properties
CallTransfer
object
18 properties 9 required
ScheduledCallback
object
21 properties 9 required
PhoneNumberImportRequest
object
8 properties 1 required
CancelWarmTransferRequest
object
4 properties
AgentCallListPage
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

speko-telephony-api-openapi.yml Raw ↑

Other APIs Speko publishes across the network.

Speko Agents API
AE Profile APIs.io
Speko Providers API
AE Profile APIs.io
Speko Voice API
AE Profile APIs.io
#Telephony
← Back to S APIs
API Details
ID
speko:speko-telephony-api
Base URL
https://api.speko.dev
Docs
https://docs.speko.dev/api-reference/introduction
Provider
Speko
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=speko-telephony-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/speko-telephony-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Speko Telephony 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.