> [!WARNING]
> **Deprecated:** Display \& Video 360 is not enrolling any new partners in Entity Read Files.

## What should I use instead?

If your team is integrated with Entity Read Files or looking for a similar tool,
consider the following:

- [Display \& Video 360 API](https://developers.google.com/display-video/bulk-tools/tools/dv360-api) offers a programmatic solution to retrieving Display \& Video 360 resource settings. Your team can retrieve a large amount of resource settings relatively quickly using bulk methods and concurrent requests. Display \& Video 360 API is the recommended replacement for Entity Read Files and a [migration guide](https://developers.google.com/display-video/api) is available.
- [Display \& Video 360 API BigQuery Connector](https://developers.google.com/display-video/bulk-tools/tools/dv3-api-bq-connector) automates the retrieval of Display \& Video 360 resource settings, similar to Entity Read Files. The data is made available in [BigQuery](https://cloud.google.com/bigquery), where your team can query wanted data.
- [Structured Data Files](https://developers.google.com/display-video/bulk-tools/tools/sdf) supports the bulk retrieval of a subset of resource types supported by Entity Read Files. Your team can manually retrieve these files using the Display \& Video 360 interface and open them in a local text editor. This solution is more practical for teams managing a relatively small number of line items.