API Modernization: UUIDs Now Live and API v1 Fully Deprecated

FEB 5, 2025

What's New

API v1 Deprecation: API v1 has been officially removed.
UUID Support for Core Resources: Messages, Phones, Users, and Agent Scripts now use UUIDs instead of numerical IDs in API v2.

GET /api/v2/messages/{uuid}
GET /api/v2/phones/{uuid}
GET /api/v2/users/{uuid}

Key Benefits

Future-proof your integrations with stable and globally unique UUIDs.
Eliminate reliance on deprecated API v1 for improved security and performance.
Improved agent experience through more accurate active call data and smoother call transitions.
Enhanced task workflows with automated message escalation from To Do’s.

Why It Matters

This release marks a major step toward modernization and reliability across the Liberty platform. With API v1 officially deprecated, all systems now operate on the more secure, consistent, and well-documented API v2. UUID implementation ensures each resource has a unique, unchanging identifier—critical for data integrity in integrations and long-term scalability.

Operationally, enhancements to active call tracking and To Do escalation bring more accuracy and automation into everyday workflows. Agents get clearer views and better handoffs, while developers gain confidence in the tools they build with.

Getting Started

Migrate from API v1: Update all integrations to use API v2. Refer to the API v2 documentation for guidance.
Use UUIDs in API v2: Update your API requests to include UUIDs instead of numerical IDs for Messages, Phones, Users, and Agent Scripts.
Explore Operational Improvements:
- Active Calls now reflect only voice-enabled agents.
- Transitions for unstarted calls and re-enqueue prevention are live.
- To Do escalations from Agent Scripts require no additional configuration.