VOYGR

Voygr POI API

Validate and enrich place data. Make business phone calls with PlaceCall. PlaceCall is the API for outbound phone calls made by an AI voice agent. Submit a…

Communication#phone

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Validate and enrich place data. Make business phone calls with PlaceCall.

PlaceCall is the API for outbound phone calls made by an AI voice agent.
Submit a task, then read the structured outcome and transcript.

Authentication

Send X-API-Key with every request. Keys carry a credit balance and usage limits.

Placing a call

POST /calls takes target_phone and a plain-language brief:

{"target_phone": "+15551234567", "brief": "Ask when the kitchen closes tonight.", "language": "en"}

The structured shape (intent + slots) and the kind and skill fields
were removed: a request that sends any of them is refused with
422 field_removed, whose removed_fields names each field and what to send
instead. Nothing is dialed or charged. The retired skills and booking
endpoints answer 410 endpoint_removed, naming the successor to use.

A 422 refusal does not dial or charge, but a balance that cannot cover the
hold returns 402 first. language accepts en, es, fr, de, hi, ru,
pt, ja, it, nl, sr, tr, pl, or auto (default); other codes
return 422 unsupported_language. A call also takes voice, disclosure,
record_call, ask_user_mode (below) and suggestion_id.

api.voygr.tech queues every call it accepts, so POST /calls answers 202
with a top-level call_id and status: "queued". The body is
QueuedCallResponse, which also repeats the ID as call.call_id. A deployment
that dials immediately answers 201 instead, and its body wraps the call, so
read the top-level call_id, else call.call_id. Poll GET /calls/{call_id}
for either. Never poll with
an empty call_id. A 404 means the ID is wrong: stop and re-read call_id
from the POST /calls response.

A timeout or a 502 is not proof that no call was placed. Send an
Idempotency-Key header (a fresh UUID per call you intend to place) and retry
with the same key and body. For 24 hours that returns the original response
with Idempotent-Replayed: true instead of dialing again. The reference for
POST /calls lists every refusal by status and error_code. A refusal places
no call and charges nothing. 409 idempotency_state_unknown and 502 are not
refusals: they cannot say whether a call was placed, and their entries say how
to check.

Reading the outcome

When status is completed, failed or cancelled, four fields say what
happened. Branch on them:

FieldQuestionValues
resultDid the call get what it was placed for?goal_met, goal_partial, refused, goal_not_met, wrong_party, not_reached, aborted, pending (an item was left open, such as a callback or a question to you that expired unanswered; items says which)
ended_byWhy did it stop?callee_hangup, agent_hangup, dropped, budget_timeout, dial_failed, customer_cancelled, system_error, compliance_stop
line_kindWhat was on the line?human, voicemail, ivr, no_answer, recorded_announcement, hold_queue
result_reasonThe detail where result alone is sharedbooked, booking_cancelled, call_dropped, short_hangup, no_engagement, agent_mute, language_barrier, busy, system_error, customer_cancelled, no_disclosure, handed_off (your client joined the call by phone)

Each is null while the call runs, and line_kind and result_reason are also
null when they add nothing. A non-null result is final for the call, pending
included: do not wait for it to change, and do not dial again because of it.
result is an open list, so a value you do not know is final too: do not read
it as a failure. outcome_summary says what happened in words,
transcript_full is the record, and outcome_charge_cents is the charge. The
outcome event and the call_completed webhook carry the four fields, but
name the summary summary and the charge charge_cents.
They add billable (the outcome family, not the bill) and charge_reason.
Neither carries the transcript: read it from GET /calls/{call_id}.

Call lifecycle

Calls are asynchronous. Poll until status is completed, failed, or
cancelled, then read the outcome above. If result is still null right
after the status turned terminal, read the call again: the outcome can land a
moment later. To be told when a call ends instead of polling, subscribe your
webhook to call_completed: PUT /users/me/webhook with
"events": ["ask_user", "call_completed"].

For live events, stream GET /calls/{call_id}/events?after_event_id=0 and
process each SSE event as it arrives. Ignore heartbeat events and comments,
keeping the last event ID when a heartbeat has no id. On a disconnect while
the call is active, reconnect with after_event_id set to the last id:
received; Last-Event-ID is not supported. A mid-call question always arrives
as an ask_user event on this stream and, when your webhook is subscribed to
ask_user (the default), also as a…

Endpoints 21

core

  • POSTValidate a place/v1/validateValidate a place's existence and operating status using evidence about the place.
  • POSTEnrich a place/v1/enrichReturn requested attributes for one place or a list of places. Standard attributes (opening_hours, phone, website, facebook, instagram, tiktok, x, email,…
  • GETView API usage/v1/usageGet current usage, quota, and reset date for the API key.
  • POSTValidate places in bulk/v1/jobs/validateSubmit 1 to 10,000 places for asynchronous validation. Each downloaded JSON Lines row follows the POST /v1/validate response contract. Save batch_id and poll…
  • POSTEnrich places in bulk/v1/jobs/enrichEnrich up to 10,000 places asynchronously using /v1/enrich request bodies. Poll GET /v1/jobs/{batch_id} until completed, then download result.jsonl.gz: one…
  • GETGet batch job status and results/v1/jobs/:batch_idStatus, progress and ETA for a submitted job. When status is completed, the response carries results.files[] with a presigned download URL (expires in about…
  • DELETECancel a batch job/v1/jobs/:batch_idRequest cancellation of a queued or running job (any type). Rows already processed are kept, billed, and downloadable; unprocessed rows are not charged.
  • GETGet the public credit rate card/v1/pricingWhat a call, a place lookup and a single-record validation cost, in credits, read from the gateway's own pricing. No key needed: quote a job before you spend.…
  • POSTSign up for a free API key/signupYou do not need a key to call this. delivery decides how the person gets theirs. email_key (the default) emails the key. The response never contains it. If…
  • POSTSwap a signup code for an API key/signup/verifyStep 2 of POST /signup with delivery: "code", also without a key. Send the verification_id and the 6 digits the person got by email. A code works for 10…

calls

  • PUTRegister the webhook for mid-call questions/users/me/webhookRegister the HTTPS endpoint we POST to when the agent needs an answer from you during a call (a hostess asking for a callback number, or an IVR wanting a…
  • DELETERemove the webhook/users/me/webhookRemove the registered URL and its secret. Mid-call questions then arrive on GET /calls/{call_id}/events and in pending_questions on GET /calls/{call_id}.…
  • GETList calls/callsList your own calls, most recent first. Each entry omits transcript_full; fetch a single call for the transcript.
  • POSTPlace a call/callsPlace an outbound AI phone call: send target_phone and a plain-language brief. The structured shape (intent + slots) and the kind and skill fields were…
  • GETGet a call/calls/:call_idPoll a single call. Returns the full detail fields (including transcript_full and transcript_status) that the list endpoint omits. The transcript is complete…
  • GETStream call events (SSE)/calls/:call_id/eventsStream live call events as text/event-stream, parsing each SSE event as it arrives rather than waiting for the response to finish. Start with…
  • GETGet your identity and quota/users/meReturns the identity and quota for this API key, with key metadata. It is lighter than GET /v1/usage.
  • POSTAnswer a mid-call question/calls/:call_id/answerAnswer a question the agent asked mid-call. If no answer arrives before the wait window elapses, the call proceeds and wraps up.
  • POSTCancel a queued or active call/calls/:call_id/cancelCancel a call that has not finished: queued, dialing or in progress. The call ends with outcome failed_cancelled. Returns {"cancelled": true} when it was…
  • POSTSuggest places to call/v1/places/suggestTurn a plain-English request ("a quiet Italian place in Wicker Park for Saturday 8pm, two people") into up to six US places to call. Each card has a dialable…
  • PUTSet the concurrent-call limit/users/me/limitsRaise (or lower) how many calls this key may have in flight at once. A call over the limit is not refused: it is accepted and waits in the queue (status…

API details

Base URL
https://api.voygr.tech
Authentication
An API key in the X-API-Key header
Operations
21 operations on 18 pathsPOST 10GET 7PUT 2DELETE 2
Main resources
calls 11core 10
Response formats
application/json text/event-stream
Description format
OpenAPI 3.1.0, API version 1.0.0

How to test the Voygr POI API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Voygr POI API collection, without the publisher's secrets.
  3. Add your credentialsThis API uses an API key in the X-API-Key header. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Validate a place” (POST /v1/validate), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Voygr POI API?

Validate and enrich place data. Make business phone calls with PlaceCall. PlaceCall is the API for outbound phone calls made by an AI voice agent. Submit a… It is listed under Communication and has 21 endpoints.

Who publishes the Voygr POI API?

It is listed from VOYGR's public API description (an OpenAPI document), not published by VOYGR on Swastik Codes. Anyone who controls voygr.tech can claim the profile by adding a DNS TXT record.

What is the base URL of the Voygr POI API?

Requests go to https://api.voygr.tech. Endpoint paths are added to this base URL.

How do I authenticate with the Voygr POI API?

With an API key in the X-API-Key header.

How many endpoints does the Voygr POI API have?

21 operations on 18 paths (10 POST, 7 GET, 2 PUT, 2 DELETE). The largest groups are calls, core.

Is forking the Voygr POI API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.