Skip to main content
applicant_trade_name contains the applicant DBA/trade name explicitly marked Used on label in the applicant box of the captured TTB COLA form. It is separate from the legal company, signatory, product brand and producer. The source spelling and punctuation are retained; a compound name is not split into inferred companies. A null value means the captured form did not provide an unambiguous marked value. It does not establish that the applicant has no trade name. The field is registration evidence, not a claim that every label image has been inspected.

​
Select a cohort

Use GET /api/v1/colas with permit_number, approval_date_from and approval_date_to. List records include applicant_trade_name; paginate until pagination.has_more is false. Query each permit separately when selecting multiple permits. Ordinary request and record quotas apply.
For a single COLA, read the same field from GET /api/v1/colas/{ttb_id}. Free-text q searches also match applicant trade names. Date defaults still apply unless you provide an explicit range.

​
SDKs, CLI and assistants

  • Python list/detail models expose .applicant_trade_name (str | None).
  • JavaScript/TypeScript list/detail results expose .applicant_trade_name (string | null; optional for older server responses).
  • cola colas get <ttb_id> displays Trade name used on label when available. --json retains the field for both colas get and colas list.
  • MCP get_cola returns it under cola.applicant_trade_name. Use existing search tools to find IDs, then retrieve details.
  • Licensed Snowflake data includes the field on the colas mart. Custom delivery schemas remain governed by their data license.