Vocily AI vs Vogent API

Vocily AI

The REST API is documented in detail for a product a few months old, with an OpenAPI 3.1 file, required idempotency keys on calls, a Retry-After header on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and two releases in September 2026 removed fields under /v1 on the day they were announced.

Vogent API

IVR detection and navigation models for outbound calls. No public changelog and no release found since January 2026.

Vocily AI

1. Send a fresh UUID in Idempotency-Key on every POST /v1/calls. The API refuses the request without it
2. Pass a from_number the workspace holds. The shared Test Number returns 403 from the API
3. Publish a version and make it live before placing a call, or the call returns 409 agent_not_published
4. Branch on detail.code, falling back to the top-level code. A 429 body is flat, so read Retry-After
5. Read currency on every call and chat record. Costs are in rupees or dollars depending on the organisation

Vogent API

1. Send an idempotencyKey on POST /dials, a reused key returns 409
2. Create a call with callAgentId, plus toNumber and fromNumberId for phone calls
3. Tell the model when to emit <|transfer|>, since transfers fire on that tag
4. Verify webhooks with the HMAC in X-Elto-Signature
5. Expect new dials to fail at the workspace's concurrent dial limit until calls end