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 10 production offices covering ~29M trademark records, with more offices planned for future phases.
OfficeJurisdictionSync FrequencyRecordsField Completeness
usptoUSDaily~14MVery high — mark text, owners, classifications, events, attorneys, filing bases
inpi-frFRWeekly~3.4MHigh — mark text, owners, classifications, events
euipoEUDaily~3.2MVery high — mark text, owners, classifications, events, Vienna codes
ipauAUDaily~2.3MHigh — mark text, owners, classifications, events
cipoCAWeekly~2.2MHigh — mark text, owners, classifications, events
wipoInternationalWeekly~1.6MHigh — mark text, owners, designations, events. Attorney data limited.
iposSGDaily~864KHigh — mark text, owners, classifications
prvSEDaily~608KHigh — mark text, owners, classifications, events
ipiCHDaily~608KHigh — mark text, owners, classifications, events
nipoNODaily~573KHigh — mark text, owners, classifications, events
Record counts are point-in-time totals from each registry. Actual ingested counts depend on sync progress and backfill status. Use GET /v1/offices to see live ingestion statistics for each office.

​
Planned Offices

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

Americas
  • IMPI (Mexico)

Europe
  • DPMA (Germany)
  • UKIPO (United Kingdom)
  • BOIP (Benelux)
  • DKPTO (Denmark)
  • PRH (Finland)
  • ISIPO (Iceland)
  • UPRP (Poland)

Asia-Pacific
  • JPO (Japan)
  • KIPO (South Korea)
  • CNIPA (China)
  • DIP (Thailand)
  • IP Vietnam

​
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": "xml",
    "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_formatIndicates the upstream data format the office published (e.g., XML, JSON, CSV). Useful for debugging parser issues.
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.
Use the updated_at field on any trademark to see when Signa last touched the record, and source_data_date to see when the office published that data. 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
  3. Check common-law sources separately (Signa covers registered marks only)
  4. Document the search date and the source_data_date from each result

​
Ongoing Monitoring

For ongoing portfolio monitoring, Signa’s daily sync frequency is sufficient for most use cases. Schedule periodic pulls against the API to detect:
  • Competitor filings of confusingly similar marks (re-run a search with filing_date_gte)
  • Status changes on your own marks (Trademark History)
  • Approaching renewal or declaration deadlines (the deadlines[] array on each trademark response)

​
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.

​
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 coverage10 offices are in production (USPTO, EUIPO, INPI France, IP Australia, CIPO, WIPO, IPOS, PRV, IPI, NIPO). 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.