API Reference
- Getting started
- Add-ons
- Analytics
- Billable metrics
- Coupons
- Credit notes
- Customer usage
- Customers
- Events
- Fees
- Invoices
- Organizations
- Payment requests
- Plans
- Resources
- Subscriptions
- Taxes
- Wallets
- Webhook endpoints
- Webhooks
List all events
This endpoint is used for retrieving all events.
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Page number.
Number of records per page.
External subscription ID
Filter events by its code.
Filter events by timestamp starting from a specific date.
Filter events by timestamp up to a specific date.
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Query Parameters
Page number.
Number of records per page.
External subscription ID
Filter events by its code.
Filter events by timestamp starting from a specific date.
Filter events by timestamp up to a specific date.
Response
Unique identifier assigned to the event within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the event's record within the Lago system
This field represents a unique identifier for the event. It is crucial for ensuring idempotency, meaning that each event can be uniquely identified and processed without causing any unintended side effects.
Unique identifier assigned to the customer within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the customer's record within the Lago system
The code that identifies a targeted billable metric. It is essential that this code matches the code
property of one of your active billable metrics. If the provided code does not correspond to any active billable metric, it will be ignored during the process.
This field captures the Unix timestamp in seconds indicating the occurrence of the event in Coordinated Universal Time (UTC). If this timestamp is not provided, the API will automatically set it to the time of event reception.
The precise total amount that was sent in the event payload. This filed is used by the dynamic
pricing model.
This field represents additional properties associated with the event, which are utilized in the calculation of the final fee. This object becomes mandatory when the targeted billable metric employs a sum_agg
, max_agg
, or unique_count_agg
aggregation method. However, when using a simple count_agg
, this object is not required.
The operation_type
field is only necessary when adding or removing a specific unit when the targeted billable metric adopts a unique_count_agg
aggregation method. In other cases, the operation_type
field is not required. The valid values for the operation_type
field are add
or remove
, which indicate whether the unit is being added or removed from the unique count aggregation, respectively.
add
, remove
Unique identifier assigned to the subscription within the Lago application. This ID is exclusively created by Lago and serves as a unique identifier for the subscription's record within the Lago system
The unique identifier of the subscription within your application. It is a mandatory field when the customer possesses multiple subscriptions or when the external_customer_id
is not provided.
The creation date of the event's record in the Lago application, presented in the ISO 8601 datetime format, specifically in Coordinated Universal Time (UTC). It provides the precise timestamp of when the event's record was created within the Lago application
Was this page helpful?