> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.pixalate.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.pixalate.com/_mcp/server. # Delivery and integration > Access, delivery methods, file formats and naming conventions, polling schedules and freshness checks for Pixalate's pre-bid data feeds. This page covers what every Pixalate data feed has in common: how you get access, how files reach you, how they're named, and how to pick up new files on time. Each feed's own page covers its schema and how to apply it. *Video (1.5 min): check, download and load a data feed file, and poll on schedule.* ## Get access Data feeds are part of your Pixalate contract. To subscribe to a feed, add one or change how it's delivered, contact your Pixalate account manager. For FTP delivery, Pixalate gives you a username and password for `ftp.pixalate.com`. Each feed is in its own folder. Some feeds have their own access terms. For example, High Risk Mobile Apps 2.0 Standard requires acceptance of updated terms, and the Enterprise version requires a subscription upgrade. See the feed's page for details. ## Delivery methods FTP is available for every feed. Some feeds can also be delivered in other ways: | Feed | Delivery methods | | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Data center feeds](/data-feeds/data-center) (IPv4 and IPv6) | FTP, Amazon S3, AWS RTB Fabric, APIs | | [High Risk Mobile Apps 2.0](/data-feeds/high-risk-mobile-apps), [High Risk CTV Apps 2.0](/data-feeds/high-risk-ctv-apps) | FTP or an Amazon S3 bucket | | [Delisted apps (DEFASE)](/data-feeds/defase) | FTP. Also available through AWS RTB Fabric, and for CTV through Amazon S3. You can look up an app's delisted status with the [Enrichment API](/apis/enrichment-api) | | All other feeds | FTP | To use a method other than FTP, or to ask whether API access is available for a feed, contact your account manager. ### Download over FTP Each file's last-modified time tells you when it was published. Check it before you download: ```bash curl --silent --head --user "USERNAME:PASSWORD" \ "ftp://ftp.pixalate.com/FEED_FOLDER/FILE_NAME" | grep "Last-Modified" ``` Then download the file: ```bash curl --user "USERNAME:PASSWORD" --remote-name \ "ftp://ftp.pixalate.com/FEED_FOLDER/FILE_NAME" ``` Replace `USERNAME`, `PASSWORD`, `FEED_FOLDER` and `FILE_NAME` with the values from your Pixalate onboarding details and the feed's naming convention. ### Download over HTTPS (WebDAV) The same server is also available over HTTPS with WebDAV. To list a folder, with each file's metadata, send a `PROPFIND` request. The response is an XML document: ```bash curl -i -X PROPFIND --user "USERNAME:PASSWORD" \ -H "Depth: 1" -H "Content-Type: application/xml" \ --data '' \ "https://ftp.pixalate.com/FEED_FOLDER/" ``` When you know the file's path, download it: ```bash curl --user "USERNAME:PASSWORD" --remote-name \ "https://ftp.pixalate.com/FEED_FOLDER/FILE_NAME" ``` To browse the files by hand on a Mac, open Finder, choose **Go** > **Connect to Server**, enter `https://ftp.pixalate.com`, and sign in with your username and password. Your folder opens on the desktop, and you can drag files out of it. ## File format Every feed is a CSV file. The columns differ by feed and are listed on each feed's page. Some files have no header row; for example, the data center feeds are a plain list of CIDR ranges. ## File naming conventions Most feeds put a date in the file name, in `YYYYMMDD` format. The data center feeds and the weekly user-agent feed use a week number instead. | Feed | File name | | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [IP block list](/data-feeds/ip-block-lists), IPv4 | `GenericIPBlacklisting_YYYYMMDD.csv` | | [IP block list](/data-feeds/ip-block-lists), IPv6 | `GenericIPv6Blacklisting_YYYYMMDD.csv` | | [Data center feeds](/data-feeds/data-center), IPv4 and IPv6 | `DatacenterSubnetsWeek[WeekNum]` | | [Proxy gateway reference list](/data-feeds/proxy-gateway) | `Gateways_YYYYMMDD` | | [Mobile device ID feed](/data-feeds/mobile-device-ids) | `DeviceIdBlacklist_YYYYMMDD` | | [CTV device ID feed](/data-feeds/ctv-device-ids) | `OttDeviceIdBlocklist_YYYYMMDD.csv` | | [High Risk Mobile Apps 2.0](/data-feeds/high-risk-mobile-apps) | `MobileHighRiskAppSelection_YYYYMMDD` | | [High Risk CTV Apps 2.0](/data-feeds/high-risk-ctv-apps) | `CtvHighRiskApps_YYYYMMDD` | | [High Risk Domains](/data-feeds/high-risk-domains) | `FraudBlist_YYYYMMDD.csv`, `PhishingMalwareBlist_YYYYMMDD.csv`, `ViewabilityBlist_YYYYMMDD.csv`, `DomainAgeBlist_YYYYMMDD.csv`, `BrandsafetyBlist_YYYYMMDD.csv` | | [Delisted apps (DEFASE)](/data-feeds/defase), mobile | `DefasedAppList_YYYYMMDD.csv`, `DefasedAppBlocklist_YYYYMMDD.csv` | | [Delisted apps (DEFASE)](/data-feeds/defase), CTV | `DefasedCtvAppList_YYYYMMDD.csv` | | [Malformed CTV bundle IDs](/data-feeds/malformed-ctv-bundle-ids) | `UnIdentifiedBundleIds_YYYYMMDD` | | [MFA data feeds](/data-feeds/mfa) | `domainMFARisk_YYYYMMDD`, `mobileappMFARisk_YYYYMMDD`, `ctvappsMFARisk_YYYYMMDD` | | [Supply path (SPO) feed](/data-feeds/spo) | `SpoBlocklist_YYYYMMDD` | | [User-agent feed](/data-feeds/user-agents) | `UAblacklisting_YYYYMMDD` (daily), `UAblacklistingWeekXX` (weekly) | Rules that apply to the names: * **Dated names carry a date only**, with no time or version. A feed that updates more than once a day publishes several files under the same date, and a newer file replaces an older one with the same name. * **Don't use the file name to find the latest file.** Use the last-modified time. * **Week numbers** restart at 1 at the start of each year and aren't zero-padded: `DatacenterSubnetsWeek1` through `DatacenterSubnetsWeek9`, then `DatacenterSubnetsWeek10` onward. ## Poll for new files Check for new files on a schedule that matches the feed's [update frequency](/data-feeds/overview#how-often-each-feed-is-updated). Each check is a last-modified request like the one in [Download over FTP](#download-over-ftp). Download a file only when it's newer than the one you have. #### Hourly feeds 1. Start checking at the top of the hour. 2. Check every 15 minutes. 3. Download when the new file is available. 4. Stop checking once you've found it, and start again at the next hour. #### Daily feeds 1. Check once every hour. 2. Download only when a new file is available. 3. Keep checking hourly after you download. More than one file is occasionally uploaded in a day. #### Weekly feeds 1. On Fridays, check once every hour. 2. Download only when a new file is available. 3. Stop checking once you've found it. Polling less often than this still works, but you pick up new entries later. At a minimum, check the hourly feeds once every hour. ## Load each new file * **Replace the whole list.** Replace the old file's contents with the new file; don't append to them. If you don't load the latest list, invalid traffic that Pixalate has since flagged gets through. * **Plan for hourly updates.** For hourly feeds, make sure your bandwidth, storage and ingestion jobs can handle a new file every hour. ## Check that your data is fresh * **Compare last-modified times.** Record the last-modified time of each file you load. If it's older than the feed's update frequency allows, your poller has missed a file or the file is late. * **Watch for cadence changes.** Changes to update frequency, file names or schemas are announced in the [changelog](/changelog). * **Report missing files.** If a file hasn't arrived when you expect it, contact [support@pixalate.com](mailto:support@pixalate.com). ## Typical file sizes Plan storage and transfer time for files up to these sizes (as of November 2025): | Feed | Up to | | ---------------------------------------- | ------ | | IP block list, IPv4 (hourly file) | 1 GB | | IP block list, IPv6 | 1 GB | | Data center feed, IPv4 | 5 MB | | Proxy gateway reference list | 1 GB | | User-agent feed | 5 MB | | Mobile device ID feed | 5 GB | | CTV device ID feed | 2 GB | | High Risk CTV app list | 1 MB | | Delisted mobile apps (DEFASE) list | 1 GB | | Delisted mobile apps (DEFASE) block list | 5.5 MB | | Delisted CTV apps (DEFASE) | 3 MB | | High Risk Domains | 5 MB | | Supply path (SPO) feed | 2 MB | | MFA websites | 2 MB | | MFA mobile apps | 1 MB | | MFA CTV apps | 1 MB | ## Related * [Pre-bid data feeds](/data-feeds/overview): which feed blocks what, and how often each is updated. * [Blocking FAQ](/data-feeds/faq) * [Fraud API](/apis/fraud-api): real-time lookups instead of lists.