Documentation Index

Fetch the complete documentation index at: https://docs.voicy.co/llms.txt

Use this file to discover all available pages before exploring further.

​

Changelog

All notable changes to the Voicy API will be documented here.

​

April 2026

​

Function-call visibility on transcripts

The transcript array returned by GET /v1/call-get/{id} now exposes the HTTP function invocations that flow-agent function nodes make during a call. Additive changes — no field removals or behavior changes on existing fields:

• New role system on transcript[].role. Previously role was always agent or caller; the enum now also includes system for flow-agent automation events. The vast majority of consumers (which iterate by role == 'agent' || role == 'caller') will see no change beyond a few extra entries they silently ignore.
• New optional field transcript[].function_invocation on system entries — carries the request method, URL, headers (sensitive values redacted), and request body captured just before the HTTP call dispatches.
• New optional field transcript[].function_result on system entries — carries the status code, response body, response headers, extracted variables, duration, and any classified error (timeout, non_2xx, ssrf_blocked, bad_response_json, type_validation_failed, invalid_url, network).

Each function-node call produces exactly two system turns (an invocation and a result), correlated by a shared invocation_id. URL basic-auth credentials, known-sensitive query parameters (api_key, token, access_token, etc.), and sensitive request/response headers (Authorization, Cookie, Set-Cookie, and anything matching token|secret|password|api_key|bearer) are redacted at capture time, so the persisted transcript is safe to share. Action required: if your code uses an exhaustive switch on the role field (case 'agent': ... case 'caller': ... default: throw), add handling for 'system' or ignore it.

​

January 2026

​

v1.0 Release

​

New Features

• Phone Call API: Create, retrieve, list, update, and delete phone calls
• API Key Authentication: Secure API access with account-scoped keys
• Dual Authentication: Support for both API keys and JWT tokens
• Dynamic Variables: Inject custom data into agent prompts
• Call Metadata: Attach custom metadata to calls for CRM integration
• Transcript Access: Full transcript available via API (text and structured)
• Recording URLs: Signed URLs for call recordings

​

Endpoints

---

​

Coming Soon

​

Planned Features

• Webhooks: Real-time notifications for call events
• Web Call API: Browser-based voice calls via WebRTC
• Agent API: Manage agents programmatically
• Phone Number API: Manage phone number assignments
• Analytics API: Call statistics and usage metrics

​

Deprecation Policy

When we deprecate API features:

1. Announcements made at least 6 months in advance
2. Deprecated features marked in documentation
3. Migration guides provided
4. Old versions remain functional during deprecation period

---