Changelog

We have released a new version of Lago with exciting new features, but also API changes likely to affect our users' workflows.

1. Replacing groups with filters

‍We have developed a new dimension system that offers greater flexibility. Filters allow users to create billable metrics with more than two dimensions, and make it easier to create charges based on custom event properties.

However, this feature introduces changes to a number of objects, including <text-code>billable_metric<text-code>, <text-code>plan<text-code>, <text-code>fee<text-code> and <text-code>customer_usage<text-code>. In addition, the endpoint to retrieve billable metric groups will be deprecated (see all changes).

2. The external subscription ID becomes mandatory for events

‍In order to develop real-time billing capabilities, we need to streamline our validation process. We have therefore decided to make <text-code>external_subscription_id<text-code> mandatory when sending events via the Lago API.

Events that only include <text-code>external_customer_id<text-code> will no longer be taken into account when aggregating usage (learn more).

3. Deprecation of API fields

‍For the sake of clarity and to preserve the quality of the API, we are going to deprecate several legacy fields (see full list).

‍Timeline

‍We will maintain the current API logic until July 9, 2024. After this date, previous versions will no longer be supported. We kindly ask our users to update their integration before that day to avoid any potential breaking change.

Migration to v1.2.0 (full post)