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

# Filter transactions by how they were created

Use a new query parameter to filter transactions by how they were created.

---

## What's new?

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

{% api-endpoint method="GET" path="/transactions?origin="  %}

- **origin** (array[string]): Return entities related to the specified origin. Use a comma-separated list to specify multiple origins
{% /api-endpoint %}

## How it works

The new `origin` query parameter lets you filter [transactions](https://developer.paddle.com/api-reference/transactions/overview.md) by how they were created. For example, you can use it to return transactions that were created using [Paddle.js](https://developer.paddle.com/paddlejs/overview.md) for [a checkout](https://developer.paddle.com/concepts/sell/self-serve-checkout.md) by passing `web`.

You can pass any valid allowed value returned by `transaction.origin`. Use a comma-separated list to return transactions that match any of the passed values.

## 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 transactions](https://developer.paddle.com/api-reference/transactions/list-transactions.md) using the API to start using the new query parameter.
## Summary of changes

| Name | Type | Change | Entity | Description |
| --- | --- | --- | --- | --- |
| `origin` | Field | added | List transactions | Filter transactions by origin. |