As announced a few months ago, this release updates the event ingestion process and removes deprecated API fields.
Changes include:
:one: Replacing groups with filters
The new dimension system based on filters is already available. It allows users to create billable metrics with more than two dimensions, and makes it easier to create charges based on custom event properties. The former dimension system based on groups is now permanently removed from the Lago API (see all changes).
:two: Marking external_subscription_id as mandatory for events
Events that only include external_customer_id will no longer be taken into account when aggregating usage (learn more). This change will streamline the event validation process and enable real-time billing capabilities.
:three: Removing deprecated API fields
For the sake of clarity and to preserve the quality of the API, we’ve deprecated several legacy fields (see full list).
:warning: Reminder: API changes
As announced a few months ago, this release updates the event ingestion process and removes deprecated API fields. Changes include:
:one: Replacing groups with filters
The new dimension system based on filters is already available. It allows users to create billable metrics with more than two dimensions, and makes it easier to create charges based on custom event properties. The former dimension system based on groups is now permanently removed from the Lago API (see all changes).
:two: Marking external_subscription_id as mandatory for events
Events that only include external_customer_id will no longer be taken into account when aggregating usage (learn more). This change will streamline the event validation process and enable real-time billing capabilities.
:three: Removing deprecated API fields
For the sake of clarity and to preserve the quality of the API, we’ve deprecated several legacy fields (see full list).
:point_right: Migration to v1.2.0 (full post)