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

Voygr Calls API

Programmatic outbound phone calls executed by an AI voice agent. Submit a task either as a plain-language brief or as a structured intent plus slots (inquiry, info_gathering, issue_resolution, booking, cancellation); the agent places the call, works through phone trees and hold, conducts the conversation in one of 13 languages, and returns a structured outcome with a full transcript. Calls are asynchronous — poll the call until it reaches a terminal state, or cursor-poll an SSE-formatted event feed for live progress and mid-call questions. A post-call merged transcript is rebuilt from the dual-channel recording. OpenAPI 3.1.0, 13 operations, X-API-Key auth, US destinations only, AI disclosure and recording notice on every call.

This API exposes 13 operations across 12 paths, organized into 2 resource areas, and defines 14 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.voygr.tech.

13 operations 12 paths 14 schemas 9 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.voygr.tech
Resource Areas
2

Paths & Operations 13

Across 12 paths, the API surfaces 13 operations — 9 GET, 4 POST. They span 2 resource areas: core, calls. Each is listed below with its method, path, parameters, and response codes.

core 2
GET
/health
Health check
health_check_health_get → 200
GET
/v1/usage
Get API usage statistics
get_usage_v1_usage_get 1 param → 200401403422
calls 11
POST
/calls
Place a call
create_call 1 param body → 201202401402403409422429
GET
/calls
List calls
list_calls 2 params → 200400401
GET
/calls/{call_id}
Get a call
get_call 2 params → 200401404
POST
/calls/{call_id}/answer
Answer a mid-call question
answer_call 2 params body → 200401
GET
/calls/{call_id}/events
Poll call events (SSE-formatted)
get_call_events 3 params → 200401404
GET
/calls/{call_id}/transcript-merged
Get the post-call merged transcript
get_transcript_merged 2 params → 200202401404
POST
/calls/{call_id}/transcript-merged/rebuild
Rebuild the merged transcript now
rebuild_transcript_merged 2 params → 200401404425503504
POST
/calls/{call_id}/cancel
Cancel a queued or active call
cancel_call 2 params → 200401404
GET
/skills
List available skills
list_skills 1 param → 200401
GET
/skills/{skill_id}/manifest
Get a skill's manifest (slot schemas)
get_skill_manifest 2 params → 200401404
GET
/users/me
Who am I / quota snapshot
get_me 1 param → 200401

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are CallDTO (19 properties), UsageResponse (13 properties), SkillRunResponse (12 properties), MergedTranscriptTurn (9 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
Error response model.
6 properties 1 required
HTTPValidationError
object
1 property
UsageResponse
object
Response model for usage endpoint.
13 properties 10 required
ValidationError
object
5 properties 3 required
TranscriptTurn
object
One line of a call transcript.
3 properties 3 required
MergedTranscriptTurn
object
One turn of the post-call merged transcript.
9 properties 5 required
MergedTranscript
object
The post-call merged transcript: both sides of the call on one timeline, built from the dual-channel call recording after the call ends. A fuller record than t…
4 properties 4 required
CallDTO
object
A call. GET /calls list entries omit transcriptfull/supervisordecisions — fetch GET /calls/{callid} for those.
19 properties 7 required
CallCreateRequest
object
Two shapes — pick one per call. Freeform: targetphone + brief (+ optional language). Structured: intent + slots (one of inquiry, infogathering, issueresolution…
7 properties
CallResponse
object
POST /calls success response (201, or 202 on deployments that queue before dialing).
5 properties 4 required
SkillRunResponse
object
POST /calls success response for the STRUCTURED (slots) path ONLY. The structured branch runs through the same pipeline as the skills engine and returns this f…
12 properties 10 required
QueuedCallResponse
object
POST /calls 202 Accepted body for the FREEFORM path ONLY, on deployments that queue before dialing. The call was persisted and credits reserved but NOT dialed…
6 properties 4 required
AnswerRequest
object
Answer a pending mid-call question. Exactly one of answer or outcome must be given — never both, never neither (server-side modelvalidator rejects both cases w…
4 properties
AnswerResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

voygr-calls-api-openapi.yml Raw ↑
Where this information came from

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