Skip to main content
Signa ingests trademark data directly from official government registries. Every record passes through a multi-stage pipeline: fetch from the office, normalize to a canonical schema, deduplicate, store, and index. This page explains what you can expect from the data and where to look when questions arise.

​
Office Coverage

Signa currently ingests from 2 production offices (USPTO, WIPO) plus EUIPO in beta, with 18 additional offices planned for future phases. Each connector is purpose-built for its office’s data format and API.
OfficeJurisdictionSync FrequencyData LagEst. RecordsData SourceField Completeness
usptoUSDaily~5 minutes~10M+ODP bulk XML (DTD v2.0/v2.3), TSDR APIVery high — mark text, owners, classifications, events, attorneys, filing bases
euipoEUDaily< 24 hours~2M+eSearch API (JSON)Very high — mark text, owners, classifications, events, Vienna codes
wipoInternationalWeekly1—7 days~1.5M+FTP country notifications (ENOTIF XML), Madrid Monitor APIHigh — mark text, owners, designations, events. Attorney data limited.
Record counts are estimates based on the total marks each registry reports. Actual ingested counts depend on sync progress and backfill status. Use GET /v1/reference/offices to see live ingestion statistics for each office.

​
Planned Offices

The following 18 offices have connector scaffolds or research in progress and will be onboarded progressively:

Americas
  • CIPO (Canada)
  • IMPI (Mexico)

Europe
  • DPMA (Germany)
  • UKIPO (United Kingdom)
  • INPI France
  • Benelux (BOIP)
  • PRV (Sweden)
  • Swiss IPI
  • DKPTO (Denmark)
  • PRH (Finland)
  • ISIPO (Iceland)
  • Norwegian NIPO
  • Polish PPO

Asia-Pacific
  • IPOS (Singapore)
  • JPO (Japan)
  • KIPO (South Korea)
  • CNIPA (China)

​
Data Freshness

Every trademark record carries a data_freshness object in the detail tier that tells you exactly how current the data is: 
{
  "data_freshness": {
    "source_data_date": "2026-03-18",
    "source_format": "dtd_v2.0",
    "last_updated_at": "2026-03-18T04:00:00Z"
  }
}
FieldMeaning
source_data_dateThe date the office’s data was current. For bulk dumps, this is the dump date. For API fetches, this is the fetch date.
source_formatThe format Signa ingested (e.g., dtd_v2.0, st96, json, enotif_xml). Useful for understanding which parser produced the record.
last_updated_atWhen Signa last wrote to this record. If this is significantly newer than source_data_date, the record was re-processed without new office data.

​
Sync Lag

The time between an office publishing data and Signa reflecting it depends on the office’s publication cadence:
OfficeTypical LagNotes
USPTO~5 minutesODP bulk daily XML; Signa syncs continuously
EUIPO< 24 hourseSearch API updated continuously; Signa syncs daily
WIPO1—7 daysFTP notifications published weekly per country
Use the updated_at field on any trademark to see when Signa last touched the record. For time-sensitive decisions (filing deadlines, opposition windows), always cross-reference with the official registry.

​
Verification Guidance

​
Trademark Clearance

When conducting a clearance search, Signa provides a strong starting point but should not be your only source. Recommended practice:
  1. Search Signa for phonetic, fuzzy, and exact matches across target jurisdictions
  2. Cross-reference high-risk results against the official registry (TSDR, eSearch, TMView)
  3. Check common-law sources separately (Signa covers registered marks only)
  4. Document the search date and the source_data_date from each result

​
Portfolio Monitoring

For ongoing portfolio monitoring, Signa’s daily sync frequency is sufficient for most use cases. Set up watches to receive alerts when:
  • A competitor files a confusingly similar mark
  • A watched mark changes status
  • A renewal deadline is approaching

​
Due Diligence

For M&A or investment due diligence, use Signa’s batch endpoint to pull full detail-tier records for an entire portfolio, then verify critical marks (high-value registrations, marks in dispute) against official sources.
Signa normalizes data from public government registries. It does not replace legal advice. Status classifications, deadline computations, and entity resolution are provided as informational tools. Always consult qualified trademark counsel for legal decisions.

​
Audit Highlights

Signa’s production connectors undergo rigorous automated and manual verification.
  • Bulk XML audit: 100% parse and normalize success on 1.5M+ records across 9 annual chunks and daily dumps
  • TSDR spot-check: 650+ records verified against live TSDR at 100% field accuracy (6,592+ field checks across 15 fields)
  • Status coverage: 167 USPTO status codes mapped, including 7 Madrid-specific codes
  • Entity types: 75+ entity type codes mapped (domestic and foreign)
  • Streaming parser: Constant ~200MB memory for any file size (tested on 4GB files)
  • Cross-validation: 10,600 records checked (8,931 verified), ~71K fields, 0 normalizer bugs
  • Test suite: 1,485 tests (unit + integration + normalizer quality + golden record + diff regression)
  • Status stages: 10 XML status stages + eSearch statuses fully mapped
  • Data coverage: 488 records enriched with full event history
  • FTP coverage: 130+ country notification directories processed
  • Event types: 10 ENOTIF event types mapped (BIRTH, DEATH, PROLONG, PROCESSED, and more)
  • Vienna codes: Leading-zero preservation verified (e.g., 0305 stays 0305)
  • Checkpoint resume: Survives crashes mid-file with {country, year, week, fileIndex, eventOffset} granularity

​
Known Gaps

No data source is perfect. Here are the known limitations:
AreaDetail
Common-law marksSigna covers registered and pending marks only. Unregistered common-law rights are not included.
Image searchDesign mark similarity search (image-to-image) is planned for Phase 2. Currently, design marks are searchable by Vienna classification codes.
Attorney data (WIPO)Madrid Monitor provides limited attorney/representative information compared to national offices.
Historical eventsSome offices provide limited event history for older marks. Recent filings typically have complete event trails.
Office coverage2 offices are in production today (USPTO, WIPO) with EUIPO in beta. 18 more are planned. For time-sensitive decisions, always cross-reference with the official registry.

​
Reporting Data Issues

If you find a discrepancy between Signa and an official registry, we want to hear about it. Include in your report:
  1. The Signa trademark ID (tm_...)
  2. The official registry and reference number
  3. The field(s) that differ
  4. A screenshot or link to the official source
Send reports to: support@signa.so with the subject line “Data Quality Report” We investigate every report. Confirmed issues are typically resolved within one sync cycle after a fix is deployed.