How to reset event data for testing

Lago has no self-service way to delete events. There is no UI control and no API endpoint to remove individual events or to bulk-delete event data, so resetting event data for a test run means asking the Lago support team to do it. Deletion happens one of two ways: by a list of specific event IDs, or by a date range.

How event deletion works

Contact Lago support and tell them what to delete using one of two methods.

To remove specific events, send a list of transaction_id values or Lago event IDs, and support deletes exactly those events. To clear everything in a window instead, send a start and end date, and support deletes all events ingested for your organization within that range.

Deleting events does not reset subscription usage counters or cached billable metric values on its own. If you need a fully clean test state rather than only the raw events gone, ask support to clear the related subscriptions or usage records in the same request, which avoids a second round-trip once you notice usage is still showing.

Recommended approach

Because each deletion goes through support, the smoothest path is to finish building and testing your event ingestion pipeline first, then request a single bulk delete before your final end-to-end validation. That keeps the validation running against a clean state and avoids repeated deletion requests mid-development.

This article reflects guidance drawn from customer case resolutions. It is not officially supported documentation and may not apply to all situations.