Trademarks

Signa normalizes trademark data from every connected office into a consistent format (see office coverage for the current list). Every trademark record includes core identity fields, classifications, owners, events, and more.

Key Fields

mark_text: The word mark as filed (may be null for design marks)
classifications: Array of goods/services classifications. Each item has nice_class (1-45) and goods_services_text describing what the mark covers
office_code: Office where the mark is registered (e.g., US, EM, WO)
filing_route: How the mark was filed: direct_national, madrid_designation, direct_regional, etc.
expiry_date, renewal_due_date: The dates the office published, null when it published none (the USPTO publishes no expiry date)
derived: Everything Signa computes from the record: the rulebook’s term end (derived.expiry_date), the maintenance schedule (derived.deadlines.items) and the opposition window. Top-level fields are always the office’s own values; computed values are always under derived.

Status Taxonomy

Every trademark office uses its own status codes. The USPTO has 200+ numeric codes. EUIPO uses 18 uppercase strings. CIPO has 30+ text-based codes. Signa normalizes all of these into a unified 4-axis status taxonomy, and always retains the office’s original status alongside it: status.raw carries the office’s code and label ({code, label}, the label verbatim, or null when we hold no verbatim office label for the code, for example USPTO codes today), List Status Codes decodes every office code, and ?include=office_extensions on Retrieve Trademark returns the office-specific fields the standard schema does not model.

The Four Axes

Every trademark status in Signa is described by four independent dimensions:

Axis	Field	Purpose
Primary	`status.primary`	High-level classification (3 values + unknown)
Stage	`status.stage`	Where in the lifecycle the mark is (18 values)
Reason	`status.reason`	Why the mark reached its current state (9 values)
Challenges	`status.challenges`	Active legal proceedings (6 values, array)

This multi-axis approach means you can filter with precision. A mark can be active (primary), registered (stage), with a null reason and [opposition_pending] in challenges: still active but facing a pending challenge.

Primary Status

The broadest classification. Every mark falls into one of:

Value	Meaning
`pending`	Application in progress, not yet registered
`active`	Registration is alive and in force
`inactive`	Registration is dead (cancelled, expired, abandoned, etc.)
`unknown`	Status could not be determined

Status Stage (18 values)

The specific lifecycle position: Pending stages:

Stage	Description
`filed`	Application received, not yet examined
`examining`	Under examination by the office
`pending_publication`	Approved, awaiting publication
`published`	Published in the official gazette
`opposition_period`	Publication period for opposition is open
`pending_opposition`	An opposition has been filed and is under review
`pending_cancellation`	A cancellation action has been filed
`pending_issuance`	Approved, awaiting formal issuance
`allowed`	Allowed (US-specific: Notice of Allowance issued)

Active stages:

Stage	Description
`registered`	Active registration, in force

Inactive stages:

Stage	Description
`abandoned`	Applicant failed to respond or gave up
`withdrawn`	Applicant voluntarily withdrew
`surrendered`	Registrant voluntarily surrendered
`refused`	Office refused registration
`cancelled`	Registration cancelled (by office or third party)
`invalidated`	Registration declared invalid
`expired`	Registration expired (not renewed)

Fallback:

Stage	Description
`unknown`	Could not be mapped

Status Reason (9 values)

Why the mark reached an inactive state. Only populated for inactive marks:

Value	Example Scenario
`refused`	Office examiner refused the application
`withdrawn`	Applicant withdrew the application
`abandoned`	Applicant failed to respond to an office action
`cancelled`	Registration cancelled by office or via proceeding
`invalidated`	Registration declared invalid after challenge
`expired`	Registrant did not renew
`surrendered`	Registrant voluntarily surrendered the registration
`revoked`	Registration revoked (EU-specific)
`other`	Reason does not fit standard categories

Challenge States (6 values)

Active legal proceedings. This is an array because a mark can face multiple simultaneous challenges:

Value	Description
`opposition_pending`	An opposition has been filed
`cancellation_pending`	A cancellation proceeding is pending
`invalidation_pending`	An invalidation action is pending
`appeal_pending`	An appeal is pending
`court_pending`	A court proceeding is pending
`other_pending`	Another type of challenge is pending

Trademark Lifecycle

The diagram shows the most common transitions. Not all edges are shown: some offices allow additional paths (e.g., direct registration without publication in certain jurisdictions).

Office-Specific Mappings

Each office’s raw status codes are mapped to the canonical taxonomy above. Here are examples from major offices:

USPTO (200+ codes)

Raw Code	Raw Label	Stage
602	Abandoned-Failure to Respond	`abandoned`
620	Backfile application added to database	`filed`
660	Approved for publication	`pending_publication`
686	Published for Opposition	`pending_opposition`
688	Notice of Allowance-Issued	`allowed`
800	Renewed Post Reg.	`registered`
900	Expired	`expired`

EUIPO (18 codes)

Raw Code	Stage
RECEIVED	`filed`
UNDER_EXAMINATION	`examining`
APPLICATION_PUBLISHED	`pending_opposition`
REGISTERED	`registered`
WITHDRAWN	`abandoned`
REFUSED	`abandoned`
CANCELLED	`cancelled`
EXPIRED	`expired`

WIPO

Event Type	Stage
BIRTH	`examining` (new designation enters examination)
PROCESSED	`registered` (protection granted)
DEATH	`cancelled`, `expired`, or `invalidated`, depending on the reason
PROLONG	`registered` (renewed)

Additional Status Fields

Beyond the four axes, the status object includes metadata:

Field	Description
`status.effective_date`	When the status last changed
`status.basis`	How the status was reached: `office` (the office stated it), `event_derived`, `dispatch_derived`, or `computed` (Signa’s projection, e.g. an IR family rolled up from its designations)
`status.raw.code`	The office’s original status code
`status.raw.label`	The office’s original status label, verbatim; `null` when we hold no verbatim office label for the code (for example USPTO codes today)

Filtering by Status

Use any combination of the four axes to filter trademarks:

“Live” marks (TESS equivalent). status_primary accepts a single value or a comma-separated list. Pass active,pending to match every mark that is either registered or still in prosecution: equivalent to the USPTO TESS “Live” filter.

# All live marks (active OR pending): TESS-style "Live" filter
curl -s "https://api.signa.so/v1/trademarks?status_primary=active,pending" \
  -H "Authorization: Bearer sig_YOUR_KEY"

# All active, registered marks
curl -s "https://api.signa.so/v1/trademarks?status_primary=active&status_stage=registered" \
  -H "Authorization: Bearer sig_YOUR_KEY"

# All marks with pending challenges
curl -s "https://api.signa.so/v1/trademarks?challenge_states=opposition_pending" \
  -H "Authorization: Bearer sig_YOUR_KEY"

# All abandoned or withdrawn marks
curl -s "https://api.signa.so/v1/trademarks?status_stage=abandoned,withdrawn" \
  -H "Authorization: Bearer sig_YOUR_KEY"

// Live marks: active OR pending
const live = await signa.trademarks.list({
  status_primary: ["active", "pending"],
});

// Active marks with pending opposition
const marks = await signa.trademarks.list({
  status_primary: "active",
  challenge_states: "opposition_pending",
});

// All inactive marks with reason
const inactive = await signa.trademarks.list({
  status_primary: "inactive",
  status_reason: "expired,cancelled",
});

Search Aggregations

The search endpoint returns aggregation counts for status_stage:

curl -X POST https://api.signa.so/v1/trademarks \
  -H "Authorization: Bearer sig_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "SIGNA",
    "options": { "aggregations": ["status_stage"] }
  }'

const results = await signa.trademarks.search({
  query: "SIGNA",
  options: { aggregations: ["status_stage"] },
});
console.log(results.aggregations.status_stage);
// { registered: 4521, examining: 892, abandoned: 234 }

Practical Scenarios

How do I find marks that are at risk of cancellation?

Filter for marks with a cancellation challenge:

GET /v1/trademarks?status_primary=active&challenge_states=cancellation_pending

How do I distinguish between refused and abandoned applications?

Use status_stage directly: abandoned means the applicant failed to act, while refused means the office denied the application. The status_reason field provides additional context.

What if an office uses a code I haven't seen before?

If an unmapped raw code is encountered, status.stage is set to unknown and status.raw still carries the office’s code and label, so you can see the original office data.

Can a registered mark have challenges?

Yes. A mark can be registered (stage) with active primary status while simultaneously having cancellation_pending or opposition_pending in the challenges array. The mark remains registered until the challenge is resolved.

Getting started

Core concepts

Build with AI

Data

Monitoring

Working with the API

Use cases

Key Fields

Status Taxonomy

The Four Axes

Primary Status

Status Stage (18 values)

Status Reason (9 values)

Challenge States (6 values)

Trademark Lifecycle

Office-Specific Mappings

USPTO (200+ codes)

EUIPO (18 codes)

WIPO

Additional Status Fields

Filtering by Status

Search Aggregations

Practical Scenarios

​Key Fields

​Status Taxonomy

​The Four Axes

​Primary Status

​Status Stage (18 values)

​Status Reason (9 values)

​Challenge States (6 values)

​Trademark Lifecycle

​Office-Specific Mappings

​USPTO (200+ codes)

​EUIPO (18 codes)

​WIPO

​Additional Status Fields

​Filtering by Status

​Search Aggregations

​Practical Scenarios

Key Fields

Status Taxonomy

The Four Axes

Primary Status

Status Stage (18 values)

Status Reason (9 values)

Challenge States (6 values)

Trademark Lifecycle

Office-Specific Mappings

USPTO (200+ codes)

EUIPO (18 codes)

WIPO

Additional Status Fields

Filtering by Status

Search Aggregations

Practical Scenarios