Source value
The literal or normalized value available from the selected USPTO/public record field.
Data Catalog
Trademark Data Fields, Definitions and Example Dataset Structure
This catalog explains the kinds of trademark fields we can work with, what they mean in a commercial dataset, and which claims we deliberately do not make about public contact or representation data.
Data provenance process
- 1Official source record
- 2Normalize with provenance
- 3Review source conflicts
Data company workflowNormalize / qualify / verify / deliver
On this page
Direct answer
What can be included in a trademark dataset?
A typical order can include identifiers, mark information, status/lifecycle fields, dates, applicant or owner fields, classification information, filing basis, representation fields and selected public correspondence/contact fields. Availability depends on the source record and the agreed scope.
Core record fields
These fields anchor a delivered row to the underlying trademark record.
| Field | Practical meaning |
|---|---|
| Serial number | Primary USPTO application identifier commonly used to bind an application record. |
| Registration number | Registration identifier when a registration exists. |
| Mark / literal element | The mark text or mark information available in the public record. |
| Filing date | Date associated with the application filing. |
| Current status | Current case-level status used for research and qualification where relevant. |
| Status date | Date associated with the current status or selected event. |
| Live/dead indicator | Broad lifecycle state; not a substitute for the more specific status and event history. |
Applicant, class and filing fields
| Field | How it can be used |
|---|---|
| Applicant / owner name | Public identity field from the trademark record. |
| Applicant / owner geography | State, country or address components when available and appropriate to the order. |
| International Class | Nice Classification class information present in the record. |
| Goods and services | Public identification text; length and normalization rules depend on the order. |
| Filing basis | Basis information such as Section 1(a), 1(b), 44 or 66(a) when present in the source. |
Representation and contact fields
Representation and contact data require careful interpretation.
| Field | Interpretation rule |
|---|---|
| Applicant attorney | Attorney field associated with applicant representation when present. |
| Examining attorney | USPTO examining attorney; this is not the applicant’s attorney and must not be treated as one. |
| Domestic Representative | A separate role that should not automatically be treated as applicant counsel. |
| Correspondence email | Public correspondence field when available. It is not automatically a verified owner-business email. |
| Phone | Included only when the source or separate enrichment scope supports it. Not guaranteed for every record. |
Download the public illustrative CSV
A free demonstration CSV is linked from the pricing page. It contains only fictional marks, masked serials with first/last digit visible, masked contact values and example timestamps. Do not confuse it with paid or verified inventory.
A free demonstration CSV is linked from the pricing page. It contains only fictional marks, masked serials with first/last digit visible, masked contact values and example timestamps. Do not confuse it with paid or verified inventory.
Illustrative delivered row
All values in this preview are synthetic, not sellable inventory. Only the first and final serial digit is displayed; correspondence contact is likewise masked.
| Field | Meaning / illustrative value |
|---|---|
| Serial Number | 9XXXXXX0 |
| Mark | EXAMPLE MARK |
| Lifecycle Event | Non-final action mailed |
| Status Date | 09/15/2026 |
| International Class | 035 |
| Representation Profile | No qualifying applicant attorney detected |
| Public Correspondence Email | c****@e******.com |
| Verified At | 2026-09-28T14:30:00Z |
Field questions
Does every record contain an email?
No. Public contact-field availability varies by record and source. An order can be scoped to require a public email only when that is supported by the workflow.
Is a correspondence email the owner’s verified sales email?
Not necessarily. We preserve the distinction between a public correspondence field and independently enriched or verified business contact information.
Can I request custom columns?
Yes, subject to source availability and the engineering/verification cost of producing the requested field.
Can the same serial number appear in different products over time?
The underlying USPTO case can experience multiple status events, but once its serial is delivered to a customer our noncompeting allocation policy does not resell it to a second customer under another product tier.
A field value and a field claim are not the same thing
Field role
What that value represents — for example applicant attorney, examining attorney, Domestic Representative or correspondence contact.
Qualification claim
The conclusion allowed by the agreed profile, such as “no qualifying applicant attorney detected.”
Enrichment claim
A separate assertion supported only when additional enrichment or validation has actually been performed.
Why provenance columns can matter in downstream work
Two datasets can contain the same-looking email or status column while meaning very different things. Provenance fields make those distinctions explicit: which source was checked, what the field represents, what rule used it and when the record was verified.
For audit-oriented orders, we can design the output so identifiers, event dates, verification metadata and selected evidence/provenance columns travel with the business-facing fields instead of being separated from them.
Build a custom data specification
Send the fields you need. If a field is ambiguous, we will define exactly what it means before the dataset is produced.