Release notes

Welcome to Ada’s release notes. Scroll down to see a list of recent releases, or subscribe to get notified about updates.

Receive a weekly email summary of releases every Friday at 11 a.m. Eastern, provided there has been at least one release that week.

Copy the following URL into your RSS reader to get notified about new releases:

https://docs.ada.cx/release-notes.rss
November 25, 2024

v2 API release

A new version (v2) of Ada’s platform APIs is now available. For detailed instructions on how to migrate your integrations, see the Migration Guide.

Alongside an updated developer documentation site, this release adds the following capabilities:

API endpoints consolidation

Several legacy endpoints have been merged and restructured by resource and action. This makes integrations simpler and reduces redundancy. For example:

  • v1: https://example.ada.support/api/end-users/v1/
  • v2: https://example.ada.support/api/v2/end-users/

Streamlined API tokens

A single API token now works across all endpoints. Previously, separate tokens were required per API. This simplifies token management and authentication.

Uniform response structures

Responses (including error messages) are now standardized. This reduces the complexity of handling different response formats and improves overall consistency.

Standardized pagination

Pagination parameters and response metadata are now consistent, improving the developer experience when handling large data sets.

Improved rate and data limits

More transparent rate and data limit policies have been introduced. This improves reliability, prevents unexpected throttling, and makes it easier to plan request volumes.

Data Export API updates

The Data Export API endpoints have been updated to follow the new v2 naming convention:

  • /api/data_api/v1.4/conversations → /api/v2/export/conversations
  • /api/data_api/v1.4/messages → /api/v2/export/messages

Backward-incompatible changes

Some v1 functionality has been deprecated or altered. Review your current integrations and ensure you’re using the appropriate v2 endpoints and parameters.