Extracting TTB Alcohol Label Approvals Past the 1,000 Result Cap

Description and use

Automation recipe for extracting TTB COLA records, bypassing the 1,000‑record limit by chunking queries, and retrieving applicant details and label images.

Problem

Automated extraction of TTB COLA records is hindered by session limits, mandatory filters, and a hard 1,000‑record server truncation.

Outcome

The recipe enables complete, programmatic retrieval of TTB COLA records, including applicant metadata and label images, while bypassing the 1,000‑record server truncation by chunking queries.

Workflow

• 1. Install apify-client and obtain an API key.
• 2. Construct a JSON payload with mode=search, optional filters (permitId, classTypeCode, originCode), dateCompletedFrom/To, includeApplicantDetails, includeLabelImages, and maxItems.
• 3. Call the actor via ApifyClient, passing the payload.
• 4. Retrieve the default dataset from the run result.
• 5. Iterate over items, extracting ttbId, brandName, applicantName, status, and labelImages URLs.
• 6. Store or process the data as needed.
• 7. Repeat with smaller date windows or additional filters to avoid the 1,000‑record limit.

Evidence

TTB forces a mandatory "Date Completed" window. The TTB backend rejects queries without a completed date range or queries spanning longer than 15 years.

Source

TTB's public registry enforces a hard limit of 1,000 records per search result window, paginated in chunks of 20 records.

Source

The TTB COLA Registry Scraper interfaces directly with the TTB public registry endpoint over HTTP without browser automation overhead.

Source