Subscribe to release notes

Webhook management API

Webhook endpoints can now be managed programmatically through the new Webhooks API. This enables automating webhook configuration across environments and integrating webhook setup into deployment pipelines.

The API supports:

• Creating, listing, updating, and deleting webhook endpoints
• Retrieving and rotating signing secrets
• Listing available event types

Webhooks created via the API are identical to those created in the dashboard and appear in both interfaces.

For details, see the Webhooks documentation.

Increased email footer character limit

The email footer character limit has been increased from 500 to 2000 characters, allowing more room for legal disclaimers, compliance messaging, and localized content.

Learn more in Email appearance settings.

Edit sync frequency and name for existing web sources

You can now edit the sync frequency and name of existing Web Import sources without needing to delete and recreate them.

Previously, these settings could only be configured during initial setup. Now you can:

• Change sync frequency between Daily, Weekly, or Never for any existing web import
• Rename knowledge sources for better organization

To update an existing web import, navigate to the Knowledge section in your dashboard, locate the web import you want to modify, and click the settings icon.

Learn more in our Web Import documentation.

View step-by-step reasoning for Playbook decisions

AI Managers can now see the reasoning behind each Playbook step selection directly in the conversation view. Click the information (ℹ) icon beside any Playbook event to see why the AI Agent chose each step.

Learn more in Playbook management.

Increased per-day rate limits for End Users and Conversations APIs

The per-day rate limit for the End Users API and Conversations API has been doubled from 30,000 to 60,000 requests per day.

This applies to:

• All /v2/end-users/<end_user_id> endpoints
• POST /v2/conversations/, GET /v2/conversations/<conversation_id>/, and POST /v2/conversations/<conversation_id>/end/

Per-minute (300) and per-second (30) limits are unchanged. No changes are required on your end.

For full rate limit details, see the End Users API and Conversations API documentation.

Configure sync frequency for web sources

Web Import sources now support a configurable sync frequency. When adding a website source, choose how often Ada automatically re-syncs its content: Daily, Weekly, or Never. Weekly is the default for all new sources.

Learn more in our Web Import documentation.

Real-time message data in the Data Export API

The Messages endpoint in the Data Export API (v2) now returns data in near real time. Previously, message data took 24–48 hours to become available — now messages are typically available within seconds of being created.

This completes the near-real-time migration of the Data Export API. Both the Conversations endpoint and the Messages endpoint now deliver data within seconds, rather than hours.

If you’re already on v2, no changes are required on your end.

For more details, see the Data Export API documentation.

Basic UI conversation view deprecated

The legacy Basic UI in the conversation view has been deprecated. The Coaching UI is now the only conversation view experience going forward. No action is required — all existing functionality remains available in the Coaching UI.

New filters for targeted analysis in MCP Server

We’ve added new filters to the MCP Server, unlocking more ways to slice conversation data for targeted analysis.

For example, you can now ask your AI assistant:

“Can you review unresolved Voice conversations from last week that used the ‘Update booking’ playbook and let me know where I should focus my improvement efforts?”

New filters include Topics, Playbooks, Coaching, Language, Channel, Browser, Device, Status Code, and Test User.

Learn more in our MCP Server documentation.

Real-time conversation data in the Data Export API

The Conversations endpoint in the Data Export API (v2) now returns data in real time. Previously, conversation data took 24–48 hours to become available — now you can query for conversations as soon as they are created or updated.

If you’re already on v2, no changes are required on your end. You can simply start fetching data earlier if you’d like to take advantage of the reduced latency.

For more details, see the Data Export API documentation.