IN
INFYNIA

Changelog

Stay up to date with the latest improvements, features, and fixes to the Infynia platform.

Subscribe to UpdatesContact Sales
v2.4.0 Live

"Added support for 5 new languages and improved interruption handling."

Why choose INFYNIA?

Enterprise-grade reliability meets cutting-edge AI technology.

Weekly Updates

We ship fast. Check back every week for new capabilities and performance boosts.

Transparent Fixes

We don't hide bugs. If we fix something, we tell you about it.

Feature Requests

Many of our updates come directly from user feedback. Let us know what you need!

High-impact Use Cases

New Models

Integration with the latest LLMs (GPT-4o, Claude 3.5) as soon as they drop.

Cutting Edge

SDK Updates

Improvements to our Node, Python, and Go SDKs for better developer experience.

Dev Friendly

Latency Reduction

Constant infrastructure tuning to shave milliseconds off response times.

Faster Voice

API changelog

Changes to the public API, newest first. Each entry says what was added, changed or fixed, and whether it can affect your integration.

  1. AddedNo breaking change in v1.

    Contacts, transcripts and recordings

    • New /v1/contacts routes (list, create, read, update, delete, import) with the contacts:read and contacts:write scopes.
    • GET /v1/calls lists calls with filters, GET /v1/calls/{id}/transcript returns the transcript and GET /v1/calls/{id}/recording a short-lived signed download URL (transcripts:read scope).
    • New contact.deleted webhook event.
  2. AddedNo breaking change in v1.

    OpenAPI reference and developer site

    • The OpenAPI 3.1 document is public at /api/v1/openapi.json, with a webhooks section for each event.
    • The /developers site publishes the guides and a self-hosted interactive reference.
    • Contract tests check every v1 route against this document.
  3. ChangedSecurityNo breaking change in v1.

    Durable and safer webhooks

    • Every delivery is retried automatically with increasing delays (6 attempts) and can be replayed by hand.
    • Signing secret rotation with a 24 h overlap: the header then carries two signatures. Without a rotation the sha256=<hex> format is unchanged.
    • A webhook is disabled after 20 consecutive failures and administrators are notified by e-mail.
    • Webhook URLs are checked against private or reserved destinations, at registration and on every send; redirects are refused.
  4. AddedChangedNo breaking change in v1.

    Common API conventions

    • Every response carries X-Request-Id, repeated in the error body.
    • Idempotency-Key is accepted on every POST for 24 h.
    • Lists use cursor pagination { data, has_more }; /v1/tasks and /v1/agents keep their historical tasks and agents keys next to data.
    • API keys gain an expiry, rotation and per-agent restriction.

Versioning policy

What we commit to so your integration keeps working.

  • The version is in the URL (/api/v1/...). v1 is stable.
  • We add routes, optional parameters, response fields, error codes and webhook event types without notice. Your client must ignore what it does not know.
  • A breaking change is only released in a new version (/v2), never in v1.
  • The previous version stays available for at least 6 months after its end is announced.
  • A deprecated route keeps answering normally and adds the Deprecation and Sunset headers, with a link to the migration notes.
  • Every deprecation and breaking change is announced here, in this changelog.
Read the versions and deprecation guideSee the API reference

Ready to transform your business?

Build a voice agent and test it in your browser in minutes.

Get Started for Free