Data Freshness & Coverage

​

Per-office sync schedule

​

Production offices

​

Italy (UIBM)

• Sync time. last_synced_at for IT on List Offices is when Signa last completed a data pull from UIBM. It is Signa’s sync time, not the date UIBM last updated its data.
• Business-day updates. Signa refreshes Italian records from UIBM on business days. Runs from Tuesday to Saturday pick up each business day’s changes.
• National marks only. Records under the IT office are Italian national marks. No Madrid designations sit under that office.
• Owners not yet resolved into entities. Owners in Italy are not yet resolved into entities at launch. Italian owners appear as individual owners until entity resolution runs, within about a week.

​

Brazil (INPI)

• Sync time. last_synced_at for BR on List Offices is when Signa last completed a data pull from INPI. It is Signa’s sync time, not the date INPI last updated its data.
• Weekly updates. INPI publishes its gazette, the Revista da Propriedade Industrial, every Tuesday. New filings and status changes reach Signa after that publication, so Brazilian data can be up to about a week behind INPI’s own search.
• Statuses as of the last gazette. Signa reads Brazilian statuses from INPI’s register export and the weekly gazette. A status that changes without a gazette notice shows once INPI publishes one. A small number of records have an unknown status, because INPI’s export leaves the status empty or the gazette has not yet stated a stage.
• Records first seen in the gazette. A record that first reaches Signa through a gazette notice carries only what that notice states, so it can lack a filing date or mark details until a later notice supplies them.

​

Mexico (IMPI)

• Sync time. last_synced_at for MX on List Offices is when Signa last completed a data pull from IMPI. It is Signa’s sync time, not the date IMPI last updated its data.
• No ownership history. IMPI publishes only the current owner of a record. Mexican records carry no earlier owners or recorded ownership transfers.
• Statuses as of Signa’s last read. Signa does not yet re-derive Mexican statuses every night. A status that changes without an IMPI filing, such as a registration that lapses at the end of its renewal grace period or an application that lapses because nobody answered IMPI, shows once Signa next reads the record from IMPI.
• Madrid designations of Mexico follow WIPO’s renewals. IMPI does not record renewals of an international registration made through WIPO, so IMPI’s own record can show a renewed designation as expired. Where WIPO shows the international registration renewed and Mexico still designated within its term, Signa shows the designation as registered, with WIPO’s term end as its expiry date and status.basis computed. Otherwise the designation keeps IMPI’s status.

​

Planned offices

​

Understanding source_data_date

# Check when a mark was last updated
curl -s https://api.signa.so/v1/trademarks/tm_abc123 \
  -H "Authorization: Bearer sig_YOUR_KEY" | jq '{source_data_date: .provenance.source_data_date, updated_at}'

const tm = await signa.trademarks.retrieve("tm_abc123");
console.log(tm.provenance.source_data_date); // "2026-03-20"
console.log(tm.updated_at);                  // "2026-03-22T10:15:00Z"

​

Consistency model

​

Detail endpoints

• Endpoints: GET /v1/trademarks/{id} and other single-resource fetches
• Source: the database. Detail reads may be served from a read replica, which can trail the primary briefly.
• Caching: trademark detail responses carry Cache-Control: private, max-age=300, stale-while-revalidate=60, so a client or proxy that honors it can keep serving a copy up to five minutes old, plus a minute of background revalidation. This cache is the main reason a detail read can trail a write. Revalidate with the ETag in If-None-Match, or skip your cache, when you need the latest state.
• Use detail reads when you need the current record, for example right after a scheduled sync or a correction.

​

Search endpoints

• Endpoints: GET and POST /v1/trademarks (list and search), sent with Cache-Control: private, no-store
• Source: the search index, which is updated from the database asynchronously
• Most changes reach search shortly after they reach the database, but an individual record can lag longer, for example after a large batch of updates.

1. When a trademark is updated, the detail endpoint reflects the change first; search follows.
2. When a search row and the detail record disagree, trust the detail record.
3. For the typical pattern (search, then fetch detail for the rows you care about), fetch detail without a cached copy if freshness matters, and compare updated_at if you need to know which is newer.

# Detail endpoint: database-backed, may be cached for up to 5 minutes
curl -s https://api.signa.so/v1/trademarks/tm_abc123 \
  -H "Authorization: Bearer sig_YOUR_KEY"

# Search endpoint: search index, updated asynchronously
curl -s -X POST https://api.signa.so/v1/trademarks \
  -H "Authorization: Bearer sig_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q": "SIGNA"}'

// Database-backed detail read
const detail = await signa.trademarks.retrieve("tm_abc123");

// Search index read, updated asynchronously
const results = await signa.trademarks.search({ q: "SIGNA" });

​

Checking office status

• last_synced_at: when Signa last completed a data pull from the office (incremental, full or backfill sync) that processed records. Detail and enrichment runs do not move it.
• update_cadence: how often Signa refreshes the office (daily, weekly, monthly or on_demand).

# List all offices with their sync status
curl -s https://api.signa.so/v1/offices \
  -H "Authorization: Bearer sig_YOUR_KEY"

# Get a specific office
curl -s https://api.signa.so/v1/offices/US \
  -H "Authorization: Bearer sig_YOUR_KEY"

const offices = await signa.references.offices();
for (const office of offices.data) {
  console.log(office.code, office.last_synced_at, office.total_marks);
}

​

Finding recently updated records

# All marks updated in the last 24 hours
SINCE=$(date -u -d '-24 hours' '+%Y-%m-%dT%H:%M:%SZ')
curl -s "https://api.signa.so/v1/trademarks?updated_at_gte=$SINCE&sort=-updated_at" \
  -H "Authorization: Bearer sig_YOUR_KEY"

const since = new Date(Date.now() - 24 * 60 * 60 * 1000).toISOString();
const recent = await signa.trademarks.list({
  updated_at_gte: since,
  sort: "-updated_at",
});

​

Known limitations