> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).

# Filter events by type

Use a new query parameter to filter events by type

---

## What's new?

We added a new `event_type` query parameter that you can use when working with [the list events operation](https://developer.paddle.com/api-reference/events/list-events.md) to return entities that match the specified event type.

{% api-endpoint method="GET" path="/events?event_type="  %}

- **event_type** (array[string]): Return events that match the specified event type. Use a comma-separated list to specify multiple event types
{% /api-endpoint %}

## How it works

The new `event_type` query parameter lets you filter [events](https://developer.paddle.com/api-reference/events.md) by the kind of event that occurred. For example, you can use it to get only [`customer.created`](https://developer.paddle.com/webhooks/customers/customer-created.md) or [`customer.updated`](https://developer.paddle.com/webhooks/customers/customer-updated.md) events if you're building a CRM integration.

It accepts a comma-separated list, so you can pass multiple event types and matching entities are returned.

## Next steps

This change is available in version `1` of the Paddle API.

It's a non-breaking change, meaning it doesn't impact existing integrations.

You can [list events](https://developer.paddle.com/api-reference/events/list-events.md) using the API to start using the new query parameter.
## Summary of changes

| Name | Type | Change | Entity | Description |
| --- | --- | --- | --- | --- |
| `event_type` | Field | added | List events | Filter events by one or more event types. |