Starting in late September 2021, the `available_on` filter will be removed from documentation to avoid user timeouts when filtering in the v1/balance_transactions API. Currently, the API times out with a 500 error after 10 seconds, resulting in a poor user experience. This filter was previously used to request a list of balance transactions based on a specified date range for the ‘available_on’ field, information that is typically used for reconciliation purposes. If you are an existing user who is already implementing this filter, there will be no visible impact on your end, but we do suggest the following alternatives to avoid timeouts.
Alternatives to using the `available_on` filter:
Use the `created` filter in list Balance Transactions API to request a list of balance transactions created in your specified date range. Ingest the data into your internal system and programmatically filter rows where the `available_on` field meets your criteria.
Use the Reporting API to run a Balance report. Use the starting date on the report to obtain a list of balance transactions which are `created` in your specified date range. Ingest the data into your internal system and programmatically filter rows where the `available_on` field meets your criteria.
Use Stripe’s Payout reconciliation report that is available from the dashboard or via the Reporting API for users on automatic payouts. If you are on manual payouts, switching to automatic payouts will give you access to this report.
Use Stripe Sigma to get SQL access to the `available_on` field on balance transactions objects without any additional setup changes or ETL.