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 to return entities that match the specified origin.
Return entities related to the specified origin. Use a comma-separated list to specify multiple origins.
How it works
The new origin query parameter lets you filter transactions by how they were created. For example, you can use it to return transactions that were created using Paddle.js for a checkout 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 using the API to start using the new query parameter.
