Changelog archive

​

October 11, 2026: screening coverage classes, usage summary window, calendar office codes

​

October 11, 2026: TypeScript SDK 0.22.0; MCP proceedings filters and compact results

​

October 11, 2026: API contract fixes

• request_id is optional on the four publicly cached single responses (GET /v1/offices/{code}, /v1/jurisdictions/{code}, /v1/classifications/{classNumber}, /v1/design-codes/{code}). They leave it out so a shared cache never hands one caller’s id to another; the cached lists already said so. Clients that validate responses against the spec no longer reject these.
• Fields the API already sent are now declared: created_at and updated_at on proceedings, revoked_at on API keys, and attorneys with attorneys_has_more on firm detail requested with include=attorneys.

​

October 11, 2026: status counts add up, and France has a pending pipeline

• Pending includes the opposition period. opposition_period records were in no bucket. They now count as pending. France’s office analytics pending_count goes from 1 to about 41,700, and market and class by_status.pending rise by the same records.
• A pending cancellation is still registered. pending_cancellation records (about 3,800, all EUIPO) were in no bucket. They now count as registered, since the mark stays on the register until the cancellation is decided. registered_count and the grant rate change for the owners, attorneys and firms that hold them (including the per-firm grant rate on GET /v1/firms/{id}/attorneys), and for the EUIPO office (registered_count, registration_rate and the registered yearly trend).
• New unknown_count. Records whose status stage is unknown (about 913,000, mostly WIPO and USPTO) now have their own count: unknown_count on office analytics, on the owner and attorney stats object, and on the analytics portfolio block, and next to by_status on market and class analytics, where it is null until those stats are next recomputed. With it, the bucket counts sum to total_marks (office, market, class), to mark_count (portfolio), or to the records counted (owner and attorney stats).
• Attorney, firm and entity active_count rise. They now count opposition_period and pending_cancellation marks as active, as owner active_count already did. The analytics portfolio.active_count does the same, so active_count, dead_count and unknown_count add up to mark_count.

​

October 11, 2026: EU legs read EU everywhere; every country filter matches every spelling

• Deadlines of EU legs. The WIPO record of a Madrid designation of the EU (stored by WIPO as EM) already read jurisdiction_code: "EU". Its deadline rows now read EU too: derived.next_deadline and derived.deadlines.items on trademarks, GET /v1/deadlines, portfolio deadlines, POST /v1/deadlines/compute (the item and its rows) and the reconcile computed context. Trademark and portfolio ETags change once.
• Webhooks. The trademark.status_changed, trademark.corrected and office_action.issued payloads carry jurisdiction_code: "EU" for that record, where they carried EM, and so does trademark_event.territory_code on office_action.issued (and territory_code on GET /v1/trademarks/{id}/events). This is the same territory written the way the trademark row writes it, not a new meaning, so payload_version does not change. Events and deliveries stored before the change read EU too: GET /v1/events/{id}, automatic retries and POST .../redeliver all serve EU (the stored copy keeps EM).
• Compute jurisdiction. jurisdiction on POST /v1/deadlines/compute reads EM as EU, UK as GB and WIPO as WO, as /v1/deadline-rules does, and the item answers with the code it was read as. UK and EM used to answer unsupported_jurisdiction. A code that is neither a country code nor known to the deadline rules (XX, ZZ) now fails only its own item, as an unknown ID does: a deadline_computation_error with id: null and error.code unknown_jurisdiction_code, while the other items are computed. deadline_computation_error.id can therefore be null. A real country with no modeled rules still returns unsupported_jurisdiction.
• Country filters. owner_country on trademark search and on the owner, attorney, firm and entity trademark lists, country_code on /v1/entities, /v1/attorneys and /v1/firms, and a watch’s filters.ownerCountry (and the same filters on the MCP tools) now match every spelling, as country_code on /v1/owners does: EU and EM both match records stored under either, as do GB and UK. owner_country=EU used to miss the owners stored as EM. Any two-letter code is accepted, an empty value is no filter, and a value that is not two letters returns 400 unknown_country_code.
• Trademark jurisdictions. jurisdictions=UK on trademark search, the party trademark lists, image search, /v1/screening, listing screening, /v1/compare and the MCP search tools is read as GB instead of returning 400 (or matching nothing), and WIPO as WO. jurisdictions=EM still returns 400 pointing at offices=EM: EM is EUIPO’s office code, and jurisdictions=EU already matches the EU legs WIPO stores as EM.
• Watches. filters.jurisdictions reads EM as EU, UK as GB and WIPO as WO (["EM"] used to fail with no_live_office). Stored watch queries are not rewritten, but evaluation and preview now treat EU and EM as one territory: a stored watch with jurisdictions EU and WIPO in its offices may now alert on WIPO’s records of EU designations, which it missed before. filters.ownerCountry must be a two-letter country code or a list of them (400 unknown_country_code otherwise); an empty value is no filter, and a value a stored watch already holds is accepted on edit. Creating, previewing or editing a watch with an owner, attorney or firm ID that was merged into another now returns 400 naming the surviving ID to watch (owner own_X was merged into own_Y; watch own_Y). A merged ID a stored watch already holds is still accepted when you edit the watch, but that watch does not alert on the merged ID’s marks while WATCH_MERGE_FOLLOW is off (the default): point it at the surviving ID.
• Cursors. A list cursor issued before this change for a request with a country_code or owner_country filter returns 400 cursor_expired once, because the filter now resolves to every stored spelling; restart from the first page.
• search_meta.warnings[].code now documents all_words_required and multi_word_retry_skipped.

​

October 10, 2026: no restoration for Madrid designations, and nothing past an expired mark’s last renewal grace

• Madrid designations get no national restoration window. A designation of Japan, the UK, Singapore, India or Iceland was served a restoration row (jp_restoration, gb_restoration, …) after its renewal grace. Those remedies restore a national renewal, and a designation renews only at WIPO: Japan’s Trademark Act Article 68-22(1) and the UK’s International Registration Order 2008 disapply them for designations, and Singapore’s International Registration Rules, India’s Trade Marks Act section 36E(4) and Iceland’s Regulation 850/2020 do not extend them to designations. A cancelled designation is now served nothing (for example IR 2015-03-10, term end 2023-07-19: the row running 2024-01-19 to 2024-07-19 is gone), and an expired one only the international renewal while its six-month grace is open. National registrations keep their restoration windows. In GET /v1/deadline-rules every restoration rule now has applies_to: "domestic", so filing_route=madrid no longer returns them. Because no restoration row follows the grace any more, a live designation inside its grace period is shown the next international renewal, as designations of other countries already were.
• An expired mark owes nothing past its last renewal grace. Once the grace period of an expired mark’s latest renewal whose window has opened has passed with no renewal on record, no row due after it is served, with or without a stated expiry_date. Before, a Philippine mark registered 2010-01-15 and expired was served, as of 2025-06-01, a declaration of use due 2026-01-15 for the fifth anniversary of a renewal that never happened. A renewal whose window is open is still served, and a renewal on record keeps the next term’s rows. On compute, an expired national mark with no renewal on record no longer lists the Philippine fifth-anniversary declaration in unsupported_rules.

​

October 10, 2026: POST /v1/trademarks accepts bodies up to 64 KB

​

October 10, 2026: lien releases cited in their text pair with their lien; owner list drops the redacted placeholder; related owners page fully

​

October 10, 2026: screening no longer clears non-Latin marks; real coverage figures; compare flags self-comparisons

• Non-Latin marks need review. GET /v1/screening matches Latin text, but a mark written mostly in another script, such as НАЙК or 耐克, could come back clear because nothing matched. When a mark’s non-Latin letters, all scripts together, outnumber its Latin letters, the screen now reports coverage.language.supported: false and the main script in coverage.language.detected, and a would-be clear becomes needs_review with the unsupported_language warning. Accented and fullwidth Latin letters count as Latin. Found conflicts still band as before. Because the verdict gate changed for these marks, their screening_id changes too; screens of Latin marks keep their ids.
• Coverage figures. coverage.horizon reported analyzed: 0 and cap: 0 on every screen. It now gives the conflicts analysed and the cap (200). capped is true when the overall horizon or a retrieval lane’s quota had more matches than it could analyse. A trademark_id screen sent without nice_classes or goods_services lists the record’s classes it searched in coverage.classes.resolved and searched instead of empty lists. coverage.lanes is reserved and stays empty.
• Self-comparison. POST /v1/compare adds a self_comparison warning to a result whose trademark_id conflict is the candidate record or another record in its Madrid family. The risk level is unchanged.

​

October 10, 2026: owner, attorney and firm search lists the real name first

​

October 10, 2026: filters from other endpoints return 400 instead of being ignored

• Filters from other endpoints. A GET request with a query parameter the endpoint does not support, when that parameter is a filter on another endpoint (offices, office, jurisdiction, q, status, nice_classes, and so on), returns 400 with code unknown_parameter. The message names the parameter this endpoint has for it, if any: deadline-rules?office=EM says to use jurisdiction.
• Common spellings. A few spellings no endpoint uses are rejected the same way: country, nice_class, query and trademark_ids.
• watch_id on GET /v1/alerts. It never filtered that list; it now returns 400 pointing at GET /v1/watches/{id}/alerts.
• Still ignored. Paging and shaping parameters (limit, cursor, include_total, sort, order, fields, include, format, language, page, per_page, offset) and other names no endpoint uses. Endpoints that already rejected unknown parameters, /v1/trademarks included, behave as before.

​

October 10, 2026: filters that match nothing now say so

• Jurisdiction codes. jurisdiction on /v1/deadline-rules and /v1/opposition-rules returns 400 for a value that is not a country or jurisdiction code, such as ZZ or USPTO. A real country with no data still returns an empty list, and historic Madrid designation codes the rules cover, such as YU or SU, keep working. jurisdictions=ZZ on trademark search also returns 400: ZZ is internal and was never a jurisdiction you could search. country_code on /v1/owners returns 400 only for a value that is not two letters; historical codes owners carry, such as DD or SU, keep working.
• Fee catalog. GET /v1/fees?office= returns 400 for a value that is not an office or country code (XX, JPO). Other offices and countries still return an empty list.
• Event types. event_type on GET /v1/trademarks/{id}/events and GET /v1/events returns 400 for an unknown type, listing the valid ones.

• Office spellings of a jurisdiction. EM is read as EU, UK as GB and WIPO as WO in jurisdiction on /v1/deadline-rules and /v1/opposition-rules. deadline-rules?jurisdiction=EM used to return only the Madrid renewal rule; it now returns the EU rules too. GET /v1/fees?office=UK now returns the GB fees.
• Owner country. country_code on /v1/owners is case-insensitive and matches every spelling owners are stored under: EU and EM both return the owners recorded as either, as do GB and UK.
• Event type case. event_type is case-insensitive: Renewal matches renewal.
• EU legs of Madrid marks. With territory_match=direct, jurisdictions=EU now also matches the WIPO record of a Madrid designation of the EU, which WIPO stores as EM. That record’s jurisdiction_code now reads EU in every mode and on trademark detail, as territory codes already did, and the jurisdiction_code aggregation and the party analytics jurisdiction_spread count it under EU.

• Every validation_error now carries an errors array. An error that is not about one field has a single entry with field (request).
• A misspelt parameter on an endpoint that rejects unknown parameters gets a suggestion: stauts says to use status_stage.
• A trademark number used as a trademark ID (GET /v1/trademarks/73120444) points at GET /v1/trademarks?q=73120444.

​

October 10, 2026: near_identical means about the same length; fewer look-alike rows for Cyrillic and Greek names

​

October 10, 2026: batch and reconcile find numbers written with separators; one IR number format

​

October 10, 2026: search says when a name of several words found little

​

October 10, 2026: reconcile no longer counts an empty register field as a mismatch

​

October 10, 2026: watch previews apply every filter; dead watch settings are rejected

• a filters.niceClasses entry that is not a class from 1 to 45 (field query.filters.niceClasses[i]). A class sent as a numeric string, such as "25", is still accepted and stored as the number 25;
• a filters.ownerId, attorneyId or firmId that is not a non-empty ID string, names no record, or names an owner Signa has retired.

​

October 10, 2026: Madrid renewal deadlines for zero-padded IR numbers

​

October 10, 2026: documentation corrected where it could lead to a wrong legal read

• US Section 71 deadlines. The guides named protection_grant_date as the trigger for US Madrid Section 71 and Section 15 deadlines. Signa computes them from registration_date. On the USPTO’s own 79-series record that is the date of the certificate of extension of protection, the date 15 U.S.C. 1141k sets for Section 71. A US designation row from WIPO’s records carries the date WIPO recorded instead, so docket from the USPTO record. With Compute Deadlines, send the certificate date as registration_date. See Deadline rules.
• Compute Deadlines operative_date_basis. The office action fact’s operative_date_basis was described as defaulting to caller_supplied. It is required and has no default; omitting it returns 400.
• US proceeding outcomes. Most ended US (TTAB) oppositions and cancellations read outcome: other, so a US win rate, including win_rate on owner and entity analytics, covers only cases decided on the record. The opposition guide, Search Proceedings and the analytics pages now say so.
• Watch preview. The quickstart showed an exact count for a US class watch that the preview could not produce then: on a busy office it reported every changed mark at the watched offices. Since the same day’s preview change (see the entry above), preview applies the class filter there too, and the quickstart shows that. See Watches.
• Record fields. filing_bases are the bases as filed; later changes are not reflected. legal_form is a normalized value (US LLCs map to corporation), not the form as filed. figurative marks can contain words in stylized lettering.
• Search. The USPTO publishes no expiry date, so expiry_date_* never matches USPTO records, and renewal_due_date_* matches only USPTO Madrid extensions (79-series) carrying the international renewal date, never a domestic Section 8 or 9 date. A name written as one word (cocacola) does not find it split by punctuation inside a longer mark (COCA-COLA ZERO); search each spelling, or send mark_text_contains without q.
• Analytics and liens. Office, market and class counts are trademark records, one per office record: a Madrid international registration counts for its own record, for each designation record, and again for any national office’s own record of a designation (such as a USPTO 79-series record). The office registration_rate is not reliable for GB. An unreleased lien can be a released one whose release cites no reel/frame. citation_issued can follow a final refusal whose text Signa has not extracted yet.
• Portfolios. Managed marks count on the daily monitoring meter, free during the beta.

​

October 10, 2026: office_action.issued fires only for USPTO examiner actions

​

October 9, 2026: US deadline corrections

• WIPO records of US designations no longer show Section 71 or Section 15 deadlines. A WIPO record designating the US (office_code: "WO", jurisdiction_code: "US") showed us_madrid_declaration_of_use_s71_first, us_madrid_declaration_of_use_s71_at_renewal and us_madrid_declaration_of_incontestability_s15 dated from the WIPO registration date. The law runs them from the date the USPTO issued its certificate of extension of protection, which only the USPTO’s own record of the designation carries. Where the US is the home office of the international registration there is no US designation at all. These records now show no rows for those rules and list each of them in unsupported_rules with the new reason computed_on_office_leg. The USPTO record of the same designation keeps its rows, dated from the US registration date. If you imported these rows from WIPO records, remove them and use the USPTO record’s rows instead.
• Supplemental Register registrations no longer show Section 15. The Section 15 declaration of incontestability is not available on the Supplemental Register (15 USC 1094), so us_declaration_of_incontestability_s15 no longer appears for a US registration whose register.type is supplemental. POST /v1/deadlines/compute takes an optional register_type (principal or supplemental) for the same result.
• Extended response and statement of use deadlines are counted from the issue date. An extended Office action response deadline now runs six months from the Office action issue date, and each statement of use extension runs from the notice of allowance (37 CFR 2.62(a)(2), 2.89), so extended dates that landed after a short month move 1 to 3 days later, to the correct date. For example, an Office action issued 30 November 2025 and extended is due 1 June 2026, not 28 May 2026.
• Maximum dates move off weekends and federal holidays. A deadline that reaches its maximum (the six-month response limit, the 36-month statement of use limit) on a Saturday, Sunday or federal holiday is now due on the next open day (37 CFR 2.196), with due_date_adjustment: "moved". Before, it was served on the closed day with not_checked. For example, a refusal of a Madrid designation sent on 25 June 2026 is due 28 December 2026, not on Christmas Day.
• An unrenewed US registration shows its term ended. When a US registration’s renewal (the combined Section 8 and Section 9 filing) is not on record and its six-month grace period has passed, derived.term.state now reads renewal_not_on_record and derived.expiry_date is the term end that passed, instead of in_term with the next ten-year renewal. The next cycle’s renewal row is no longer shown. This applies only when Signa has the registration’s USPTO prosecution history, that history records at least one Section 8 or Section 9 filing (such as the six-year Section 8; a Section 15 filing does not count), and the USPTO status does not say the registration was renewed. For a past computation date, only filings and a status dated by then count. The USPTO keeps such a registration “registered” until it cancels it, usually within a few weeks; Signa’s status keeps the office’s value until then.

​

October 8, 2026: an attorney’s firms come from its filings

​

October 10, 2026: a listed GLEIF ultimate parent passes its ticker to subsidiaries

• Entities. Retrieve Entity shows a listing block with status: "subsidiary_of_listed", the ultimate parent’s ticker and LEI, publicly_traded: true, and the ticker in tickers. ticker= on Search Entities and Search Owners, and publicly_traded=true on Search Entities, match it.
• The direct chain still wins. When the direct-parent chain reaches a listed company, that company stays the listed ancestor.
• The newest ultimate parent counts. GLEIF reports one ultimate parent at a time. When older ultimate-parent records are still present, only the most recent one is used: if it is not listed, the entity gets no inherited ticker. If two or more different companies share the most recent start date, the entity gets none.
• Timing. Listing data refreshes with the weekly GLEIF update, so these entities change after the first weekly refresh following this release. Entity search and detail, and owner search and detail, show the change the same day. The owner_ticker and owner_publicly_traded filters on trademark search and on watches follow within about a week, when the weekly public-company check refreshes each affected trademark.
• Unchanged. Entity Family and include_family still follow direct parent and subsidiary edges only.

​

October 8, 2026: a filing shows only the firm it names

• Trademark detail and batch. attorneys[].firm_id and firm_name are the firm the filing names, and null when it names none. attorneys[].address is the address on the filing, and null when the filing has none. WIPO, PRV (Sweden) and Italian records never carry the address on the filing, so they keep showing the attorney’s address on file.
• Madrid international registrations. The detail lists an attorney once per firm its designations name, each row with the territory_codes of the designations naming that firm. Designations that name the attorney with no firm get their own row with firm_id: null; they no longer take another designation’s firm.
• Search. The firm_id filter and facet match only filings that name the firm. attorney_firm_name matches the firm name the filing states for its first (primary) attorney.
• Watches. A watch filtered by firm_id or attorney_firm_name matches fewer marks once the search index is rebuilt: only the filings that name the firm.
• Firm totals. trademark_count, active_count and the other counts on /v1/firms and /v1/firms/{id} count the filings that name the firm. attorney_count counts the attorneys on those filings. Firms credited through borrowed firms drop sharply: a firm that showed 5,031 trademarks can now show 3. A firm that no filing names has no counts.
• Firm attorneys. GET /v1/firms/{id}/attorneys and GET /v1/firms/{id}?include=attorneys list the attorneys with at least one current filing that names the firm. Each row’s trademark_count, grant_rate and latest_filing_date cover the filings naming this firm, not the attorney’s whole portfolio, and the list is sorted by that count. firm_name is this firm’s name.

​

October 7, 2026: renewal deadlines for Madrid designations without their own rules

• A Madrid designation of the EU, WIPO’s EM record or the EUIPO’s EU record on the Madrid route, is not served the EUIPO renewal (eu_renewal) or restitutio (eu_restitutio): the EUIPO does not handle renewal of international registrations designating the EU. On the EUIPO’s records this changes the rule, the consequence (lapse_of_international_registration), the calendar (wipo_geneva, so a due date on a EUIPO-only closure day such as 1 May no longer moves) and drops the restitutio row. Both EU rules now read applies_to: "domestic" in the catalog. EU trade marks filed at the EUIPO keep their dates; their rows’ last_verified reads 2026-10-07 and the EU sources no longer list the Madrid Protocol citation that covered the designation case.
• On the EUIPO’s records of Madrid designations of the EU, each renewal row’s occurrence_key starts with the new rule_id (madrid_designation_renewal: where it read eu_renewal:), so it changes once. The portfolio iCal feed builds its event UID from that key, so a subscribed calendar sees each such event replaced once: the old event removed and a new one added. Any eu_restitutio event is removed.
• POST /v1/deadlines/compute and POST /v1/reconcile apply the same rule to the items you send. {"jurisdiction": "EU", "filing_route": "madrid"} now returns madrid_designation_renewal where it returned eu_renewal (and no eu_restitutio row), and a Madrid-route item coded RU, EM or any other served code is now supported where it read reason: "unsupported_jurisdiction". The prosecution half (facts[]) is unchanged: an EU Madrid item keeps the EUIPO provisional-refusal rule (euipo_madrid_oa_response), and a jurisdiction without its own rules still reads unsupported_jurisdiction for every prosecution type, with no stated_deadline row served.
• The schedule is the renewal only. Cabo Verde, Cambodia and Mozambique also require use declarations filed with their national office (WIPO Information Notices 27/2022, 11/2016 and 37/2016), which are not computed; every row of such a designation says so in its note, naming the notice.
• A designation whose status stage is unknown (about 143,000 of these WIPO records, 49,681 of them Jersey) is served like any other record, with one exception: it is not credited a later expiry WIPO published for its international registration, because that renewal may have left it out. It keeps the term WIPO states for it, lapsed or not. On 7 October that held back 211 records whose family showed a later term. The same now applies to Madrid designations in jurisdictions with their own rules (16 records on 7 October).
• A designation that WIPO reports refused, invalidated, surrendered, cancelled or expired past its grace gets no later renewal. One with neither an international registration date nor a stated expiry returns reason: "requires_office_date". National records of these jurisdictions, and every other jurisdiction that has its own rules, are unchanged.

​

October 6, 2026: Portugal (INPI) deadline rules

​

October 6, 2026: class suggestion and goods and services on every plan

​

October 5, 2026: rank many spellings in one search with a list in q

curl -G "https://api.signa.so/v1/trademarks" \
  -H "Authorization: Bearer $SIGNA_API_KEY" \
  --data-urlencode 'q=["onyx","0nyx","onix"]' \
  --data-urlencode "similarity=identical,lookalike"

• Look-alikes are found. With lookalike, onyx also finds 0NYX (a zero for the O). Before, a list in q was an alias of mark_text_is, an exact filter, and missed such marks.
• Limits. Up to 100 names when similarity is only identical and lookalike. With fuzzy, embedded or phonetic, including the default, up to 10 names and 30 words in total. More than 100 names returns 400 with code: too_big. More than 10 names or 30 words with those channels returns 400 with code: too_complex, naming the fix.
• Same price. A list costs 10 credits per page, like any search.
• Not a number lookup. A list is never read as a trademark number; use Batch Retrieve.
• Pages are ranked across all names. A name with no hits on the pages you read is not proof that it is clear: page to the end, or search that name on its own.
• Owner, attorney, firm and entity /trademarks lists take one search text; a list there returns 400.

​

October 5, 2026: owner list ticker and lei match the owner’s detail

• ticker matches any of the owner’s tickers: its own SEC tickers or, when it has none, its entity’s (the members’ SEC tickers and the entity’s listing ticker, which can be inherited from a listed parent). This is how GET /v1/entities?ticker= matches an entity. The ticker on the owner’s detail is always one of them. Matching is case-insensitive.
• lei matches any of the owner’s LEIs: its own GLEIF LEIs or, when it has none, its entity’s (the entity’s own LEI and the members’ LEIs). The lei on the owner’s detail is always one of them. Matching is case-insensitive.
• A ticker on a GLEIF record is not one of the owner’s tickers, as on detail, so it no longer matches ?ticker=.
• An owner whose entity is no longer served (GET /v1/entities/{id} returns 404) is matched on its own company matches only.

​

October 5, 2026: MCP list_proceedings filters by party owner or entity

​

October 4, 2026: Deadline coverage for expired, cancelled and dead marks; reconcile names declined rules

• Expired and cancelled marks name the rules they can still be served. A mark that has expired or been cancelled was registered, so a deadline that runs from the registration date (or, in Brazil and Mexico, the grant date) is owed when the mark’s status can still be served it. An expired mark is served any rule whose miss costs something while that rule’s window is open; a one-off declaration of a national mark (such as US Section 8, the Philippine third- and fifth-year declarations or the Mexican third-year declaration) closes before its term ends, so an expired national mark is not asked for its date, while a Madrid designation granted late in the term of its international registration still is. A cancelled mark is served only a renewal that opens a restoration window Signa models (EU, GB, IS, IN, JP, SG); of those renewals only Japan’s runs from the registration date, so a cancelled Japanese mark is the one that can lack it. With include_missed: true on POST /v1/deadlines/compute, and always on POST /v1/reconcile, both statuses also owe every rule whose missed cycle would be returned, provided some date the mark could carry would return its row as of the computation date (a US mark cancelled three years after filing owes no Section 8 or 9 date yet). A Mexican national mark registered before 10 August 2018 is never asked for its grant date for the third-year declaration, which covers later grants only; a Madrid designation still is, since its statement of grant can come years after its international registration. Before, such a mark with no registration_date or grant_date was reported as supported: true, and the rules it could not compute were not named. Now, when it owes such a rule and no rule can be computed, it reads supported: false with reason: "requires_office_date" on POST /v1/deadlines/compute and in derived.deadlines, and it is listed in unsupported_marks on GET /v1/deadlines and portfolio deadlines, as a registered mark with the same missing date already was. For example, the compute item { "jurisdiction": "US", "status": "expired", "filing_date": "2010-01-04" } returns supported: false. With "status": "cancelled" it stays supported: true with no deadlines, because the US models no restoration; add "include_missed": true and it returns supported: false, since its missed Section 8 and Section 9 cycles need the registration date. When some rule can still be computed, the mark stays supported and the owed rules it cannot compute are listed in unsupported_rules (and the mark in unsupported_marks). For example, a Philippine national mark with status expired, a filing date and no registration date lists ph_renewal, ph_declaration_of_use_renewal and ph_declaration_of_use_mid_renewal (and, with include_missed: true, ph_declaration_of_use_5yr, whose missed row would be returned). Send the registration date and those rules are computed; an office-stated expiry date anchors only the renewal.
• A mark whose status ends every obligation is never declined. An abandoned Australian direct mark filed before 1996, a withdrawn Singapore direct mark filed before 15 January 1999, and a refused Madrid designation with no international registration date read supported: false with reason: "requires_office_date" on compute and in derived, while unsupported_marks left them out. They now read supported: true with no deadlines, like other abandoned, withdrawn, surrendered, invalidated or refused marks in a jurisdiction Signa models. A mark in a jurisdiction Signa does not model still reads unsupported_jurisdiction, and a refused WIPO international registration record keeps its renewal deadline, because a provisional refusal does not end the international registration.
• POST /v1/reconcile names declined rules. With verdict_detail: true, computed now carries unsupported_rules, in the same shape as on POST /v1/deadlines/compute: the rules that apply to the record but were declined because it lacks the date the statute anchors them on. For example, a Philippine Madrid designation with no statement of grant of protection lists ph_declaration_of_use_5yr_madrid with missing_field: "protection_grant_date". Before, computed said supported: true with no trace of the declined rule, and a docketed deadline for it could not be told apart from one with no matching occurrence. The field is additive and is [] when nothing was declined. See Reconcile.

​

October 4, 2026: portfolio events include status corrections

• Webhooks. Every endpoint subscribed to trademark.status_changed also receives trademark.corrected. The envelope type is trademark.corrected, so you can tell a correction from news. trademark.corrected is also accepted in enabled_events on its own (corrections only). Your stored enabled_events does not change.
• Events feed. GET /v1/events lists trademark.corrected events by default, and, as on webhooks, event_type=trademark.status_changed includes them. event_type=trademark.corrected returns corrections only.
• Payload. data is the trademark.status_changed body plus correction: { kind }, where kind is status or late_office_record. See trademark.corrected.
• Watches are unchanged. A watch still receives trademark.corrected only when its trigger_events lists it.

​

October 4, 2026: firm counts follow the firm of record

​

October 4, 2026: a linked owner’s ticker and LEI come from its entity

• publicly_traded and has_lei equal the entity’s. publicly_traded is also true when the entity is itself listed or is a subsidiary of a listed company.
• ticker is the owner’s own first SEC ticker. When it has none, it is the entity’s ticker, which can be a ticker inherited from a listed parent.
• lei is the owner’s own first GLEIF LEI. When it has none, it is the entity’s lei: the entity’s own LEI when set, else the first member LEI.
• companies[] lists the same matches, the owner’s own first.
• When the entity was merged into another, the facts are the surviving entity’s. When the entity is no longer served (GET /v1/entities/{id} returns 404), the owner reports only its own matches and companies_source is direct.
• GET /v1/owners/{id}/related walks the one lei the owner’s detail shows: its own first LEI, else its entity’s. An owner with several LEIs of its own used to walk all of them, and an owner with none walked nothing.
• Owners not linked to an entity are unchanged. The MCP get_owner and get_owner_related tools return the same values. See Retrieve Owner.

​

October 4, 2026: status corrections arrive as trademark.corrected; status basis relabels raise no alert

• A status Signa corrects. When Signa fixes a status it published wrongly, for example a mark shown as expired that the office records as renewed, the status change arrives as trademark.corrected instead of trademark.status_changed or trademark.updated.
• Late office records. When office records reach Signa late and show a mark lapsing, or a dead mark returning, the change arrives as trademark.corrected too.
• Other changes in a correction raise no alert. Any other change Signa stores while correcting statuses or catching up on late office records, including marks Signa first learns of from late records, updates the mark but raises no alert.
• Status basis relabels raise no alert. A change that only relabels where a status comes from (status.basis, for example office to computed) no longer raises a trademark.updated alert. The mark shows the new basis.
• MCP. The signa_alerts_list tool’s event_type filter now accepts trademark.retracted and trademark.corrected, like GET /v1/alerts.

​

October 4, 2026: derived.term and no projected term past a lapsed expiry

• New derived.term on trademark detail, batch lookup, search results, portfolio rows, watch previews and the MCP get_trademark tool: state (in_term, in_grace, in_restoration, renewal_not_on_record or not_applicable), grace_expiry_date, restoration_expiry_date and renewed (whether a renewal on record began the term). See The term on record.
• derived.expiry_date stays at the office-stated term end once it has passed, while the mark can be renewed late or restored and, with term.state: "renewal_not_on_record", after that. While a restoration window is open it is that date (it was null). A renewal the office recorded (including one recorded after the grace period), or for a Madrid designation (a national office’s record, IP Australia’s for example, or WIPO’s own) an expiry WIPO published for the international registration in a later term, moves it forward to the next term, which reads in_term. The rows of that designation keep the office’s own dates as their trigger.
• No renewal is computed past such a term end. derived.deadlines.items and derived.next_deadline drop the projected later cycles and the restoration of a cycle that never began. The same applies to GET /v1/deadlines, portfolio deadlines and the iCal feed, POST /v1/deadlines/compute and POST /v1/reconcile, whose computed expiry_date is now the lapsed term end.
• An office that reports a mark expired the day after its term ends (the UK office does) reads in_grace, then in_restoration, until those windows close.
• status and the top-level expiry_date are the office’s and do not change. A schedule with no office-stated expiry (every USPTO record) keeps the statutory term end.

​

October 3, 2026: China Madrid opposition windows from 2027; Philippine and Mexican office closures

• China, Madrid designations: two months from the WIPO publication from 2027. CNIPA published draft transitional measures for the revised Trademark Law for comment on 28 September 2026. They are not in force yet. Under the draft, an international registration whose WIPO Gazette date is on or after 1 January 2027 gets the revised two-month opposition period counted from the publication. The draft does not say whether the current start, the first day of the month after the Gazette, survives, so cn_opposition_madrid serves those registrations the window both readings allow: it opens on the first day of the following month and closes two months after the Gazette date. For a Gazette date of 15 January 2027 the window is now 1 February to 15 March 2027, where it was 1 February to 30 April. Registrations published before 2027 keep three months from the first day of the following month. The shorter window is served first because a close that turns out early costs an opponent nothing, while one that turns out late costs the right. If the final measures differ, the rule follows them. On GET /v1/opposition-rules the rule now has window_change_date: "2027-01-01", window_months: 2, window_starts_on: "day_after" and the new field window_opens_on: "first_of_following_month" (null on every other rule), and the earlier era moved to window_months_before: 3 and window_starts_on_before: "first_of_following_month". The draft measures and the consultation notice are among its sources. See opposition rules.
• Philippines: IPOPHL closed on 16 to 18 November 2026. Proclamation No. 1447 declares those days non-working in Metro Manila, where IPOPHL has its office. A Philippine opposition window that closed on 14 to 18 November 2026 now closes on Thursday 19 November 2026, with close_adjustment: "moved".
• Mexico: four IMPI suspensions of time limits. IMPI suspended all its time limits on 8 and 9 August 2024, 18 May 2026, 23 September 2026 and 25 September 2026, by notices in the Diario Oficial de la Federación. Mexican opposition windows and renewal deadlines that fell on those days now move to the next working day. GET /v1/deadline-rules lists the four notices among the Mexican sources.

​

October 3, 2026: proceedings party owner and entity filters return linked proceedings

• party_owner_id, party_entity_id and entity_id on GET /v1/proceedings return results. They match proceedings where a party is linked to the owner, or to any member owner of the entity. Combined with q or party_role, every filter still has to match the same party.
• Parties without a link are not returned by these filters. They include most Canadian and Australian opponents (they are matched only against the owner of the mark under challenge), a name that matches only without its company suffix, and a recorded name that lists several parties. Search with q to match by name or for complete coverage. See Search Proceedings.
• parties[].owner_id on proceedings now carries the linked owner, reported as its current owner record (the surviving owner if it has since been merged), and stays null for a party without a link.
• Owner and entity analytics count challenger disputes. litigation.as_challenger on owner and entity analytics counts the disputes where a linked party is the opponent or petitioner, so it is no longer always 0. proceedings_total changes with it.

​

October 2, 2026: USPTO post-registration office actions get their response deadline

• New row type post_registration_oa_response (rule_id: "uspto_post_registration_oa_response"), due six months after the action or at the end of the filing period the action examined, whichever is later, moved off weekends and federal holidays. It appears in derived.deadlines and derived.next_deadline on trademark detail, batch lookup, search results and portfolio rows, on GET /v1/deadlines (new type=post_registration_oa_response filter value), on portfolio deadlines and the iCal feed, on POST /v1/deadlines/compute for stored trademark ids, and on the MCP get_trademark tool. occurrence_key is uspto_post_registration_oa_response:<action date>:<action code>.
• New optional note field on deadline rows. Present only when the record adds something the dates do not say: the action a response row answers (PRA8 2026-04-19), a “no response required” notice, or a prosecution history that could not be read.
• The row closes only on explicit evidence: a response naming the action’s section, the office’s acceptance of the examined filing, or a cancellation of it. A notice of incomplete response reopens every row it could concern. If the response date passes with nothing on record, the row stays as missed; the examined declaration or renewal row is not changed. Whether the registration was lost is read from its USPTO status.
• When the record cannot settle the date (the examined filing is not on record, a notice of incomplete response has no action on record, or the action predates 2015), the row stays open on the earliest date Signa can defend, with a note to check TSDR. A served date never moves later.
• An action still open more than a year after its response date, on a registration whose current status is registered, is treated as resolved by the USPTO: no row.
• On POST /v1/deadlines/compute for a stored id, prosecution_deadlines now dates this rule from the stored history, and support reports it as computed instead of facts_required. due_date is six months from the action, as on caller-supplied facts, and effective_due_date is the date the row serves. A closed one carries closed_by: "response", or the new value closed_by: "acceptance" when the office accepted the examined filing, with closed_by_fact_id: null (the closing entry is named in notes).
• GET /v1/deadline-rules and the MCP get_deadline_rules tool list the rule. See USPTO post-registration office actions.

​

October 1, 2026: records from offices that are not live yet are no longer served

• Search and list. GET and POST /v1/trademarks, in both grouped and expanded views, leave these records out of rows, pagination.total_count and aggregations. The same applies to GET /v1/trademarks/suggest, screening, image search, the owner, attorney, firm and entity trademark lists, and the MCP search and list tools. An office number or a tm_ id in q does not return such a record.
• Lookups by id. GET /v1/trademarks/{id} and its events, proceedings, assignments, documents, citations and cited-by sub-resources return 404. POST /v1/trademarks/batch lists the id in not_found. GET /v1/deadlines?trademark_id=, POST /v1/deadlines/compute, POST /v1/compare and screening by trademark_id treat the record as not found. The MCP get_trademark, batch_get_trademarks, get_trademark_events and get_trademark_proceedings tools answer the same way.
• International registrations stay. A WIPO international registration is a record of a live office, so it is still returned with all of its designations, including designations of a country whose national office is not live yet. The national office’s own record of that designation is not returned on its own. Image search matches images by their own record’s office, so an international registration whose only image sits on such a national record is not found by image search.
• Unchanged. offices= and office_code filters naming an office that is not live still return 400 with unknown_office_code. jurisdictions= with such a country still returns the rights of live offices that protect it, such as EU trade marks and Madrid designations. Marks already in a portfolio stay in it, are listed, and keep their portfolio deadlines.

​

October 1, 2026: proceedings q matches the party you filter by; party owner filters return no results (superseded October 3, 2026)

• Behavior change. On GET /v1/proceedings, q and party_role now have to match the same party. q=Acme&party_role=opponent returns proceedings where a party named Acme is the opponent. Before, it also returned proceedings where Acme was the respondent and anyone else was an opponent, so the list could include cases from the wrong side. q combined with party_owner_id or party_entity_id follows the same rule. q alone and party_role alone are unchanged.
• party_owner_id, party_entity_id and entity_id return no results today. Proceeding parties keep the name the office recorded but are not yet linked to owner or entity records, so these filters match nothing. They stay accepted. Search by name with q, which matches a case-insensitive substring of the recorded party name; it does not add related companies or subsidiaries. Search Proceedings and the opposition guide now use q in their examples. Superseded October 3, 2026: these filters now return proceedings whose parties are linked; see that entry.
• The party_role aggregation still counts every role on the matching proceedings, so q=Acme&party_role=respondent can show an opponent bucket: it counts the cases that had an opponent.

​

October 1, 2026: Australia, Norway, Sweden and Singapore show as covered on /v1/jurisdictions

​

October 1, 2026: USPTO declarations and renewals on record close their deadlines

• A filing made inside its window (from the day the window opens to the end of the grace period) closes that cycle on derived.deadlines and derived.next_deadline on trademark detail, batch lookup, search results and portfolio rows, on GET /v1/deadlines (including urgency=missed), on POST /v1/deadlines/compute for stored trademark ids, on portfolio deadlines and the portfolio iCal feed, on POST /v1/reconcile and on the MCP get_trademark tool.
• The combined Section 8 and 9 renewal closes only when both parts are on record.
• derived.expiry_date and the term end POST /v1/reconcile compares against move to the next term only when the USPTO accepts the renewal, not when it is filed.
• A Section 15 declaration whose window has passed is no longer listed as missed (urgency=missed, include_missed). Section 15 is optional and can be filed after any later five-year period of continuous use, so nothing is lost. An open Section 15 window is still served.
• A US designation ingested from WIPO’s records is not covered yet. See USPTO filings already on record.

​

October 1, 2026: offices declare proceedings support; proceedings come only from those offices

• GET /v1/proceedings and the MCP list_proceedings tool with an office_code for a live office whose capabilities.proceedings is not available return 422 capability_not_available, with capability, capability_state and office_code in the error. No query runs and no credits are charged. Before, such a request could time out, or return an empty list that looked like “this office has no proceedings”.
• A proceeding_type that no served office records (today court_action), or that the requested office_code does not record, returns an empty page and empty aggregations buckets straight away, charged as a normal page. Search Proceedings lists the types each office records.
• The proceedings endpoints return proceedings only for offices whose capabilities.proceedings is available: the GET /v1/proceedings list, GET /v1/proceedings/{id} (a proceeding from any other office is 404), GET /v1/trademarks/{id}/proceedings, the proceedings_count on a trademark’s detail, and the MCP get_proceeding, list_proceedings and get_trademark_proceedings tools. Two signals catch up after this release:
  • aggregations counts on GET /v1/proceedings may still include proceedings held for offices that are not live yet, until a follow-up backfill completes. The listed proceedings never include them.
  • Search and screening signals that come from the search index (the has_proceedings filter, the ranking boost for marks with proceedings, and screening’s prior-proceedings and litigious-owner signals) apply the same rule to each mark when it is next indexed. Until then, an international registration whose only proceedings sit on a designation in an office that is not live yet can still match has_proceedings=true.
• The GET /v1/offices and GET /v1/offices/{code} ETags change once, because the body gained a field.

​

October 1, 2026: any API key can connect to MCP

• initialize and tools/list work for every session. tools/list returns every tool, including ones the session can’t call.
• get_account and get_credit_pricing work for every key.
• A tool the key lacks a scope for returns the forbidden error REST returns (status 403, naming the scope) with the call’s request_id, and is not charged.
• An invalid, revoked or expired credential still gets 401. Rate limits and the batch cap are unchanged.

​

October 1, 2026: deadline corrections for lapsed marks and Swiss, Polish and Norwegian opposition windows

• A lapsed mark is no longer served a renewal ten years out beside its restoration window. Some offices keep a mark at registered for months after its stated term ended. When the office states a term end that has passed and a restoration window is on the schedule, derived.deadlines on trademark detail, GET /v1/deadlines, POST /v1/deadlines/compute and POST /v1/reconcile now serve the lapsed renewal while it is in grace and the restoration window, but no later renewal cycle. After the grace period, and while the restoration window is open, derived.expiry_date is null. The office’s status and expiry_date are unchanged. A mark the office has renewed, or whose stated term end is still ahead, is not affected. See Restoration periods.
• Switzerland: no opposition window before the Trade Mark Protection Act. Opposition in Switzerland exists since the Act commenced on 1 April 1993 (MSchG art. 79). A Swiss publication dated before that day, national or Madrid, now has no window instead of a three-month one. A national mark filed before that day has none either, whatever its publication date (MSchG art. 76(2)(c)); this needs the filing date, which trademark detail uses and which POST /v1/oppositions/compute reads from filing_date.
• Poland: no opposition window before pre-grant opposition existed. Pre-grant opposition in Poland began on 15 April 2016 (Dz.U. 2015 poz. 1615 art. 3). A national publication dated before that day, or a national application filed before it (art. 2 ust. 1 of the same Act), now has no window instead of a three-month one. Madrid designations of Poland were already gated at that date.
• Norway: two months for registrations published before 1 July 2010. The repealed 1961 Trademarks Act § 21 gave two months from publication, so the window for a registration published before 1 July 2010 now closes one month earlier and cites that Act. Every window in that group closed years ago.
• New reason before_commencement on POST /v1/oppositions/compute. When an opposition rule exists for the office but the item was published, or filed, before the date the rule applies from, the item now returns reason: "before_commencement" with the rule’s rule_id and effective_from. Before, it read unsupported_office, which suggested no rule existed for the office. The same applies to rules that already had a start date, such as Vietnam’s and Mexico’s. unsupported_office now means only that no rule exists for the office and route. Trademark detail is unchanged: derived.opposition_window.reason keeps unsupported_office for these records.

​

October 1, 2026: MCP search tools take date ranges and field projection

​

October 1, 2026: documentation corrected against the API

• Freshness. Trademark detail reads were described as strongly consistent. They carry Cache-Control: private, max-age=300, so a cached detail read can trail a write by up to five minutes, and they may be served from a database read replica. See Data Freshness.
• Search depth. Not every search stops at 10,000 rows: a grouped request without q pages by key, with no fixed depth. A position walk can repeat or skip a row when records change between pages, so deduplicate on id. See Search depth.
• Harmonised terms. is_harmonised: true marks a term from a harmonised list (the EUIPO Harmonised Database, or a TM5-harmonised USPTO ID Manual entry). It does not mean every TM5 office accepts the wording; read accepted_offices. The harmonised_only description on GET /v1/goods-services and the MCP tool now says the same.
• Entity portfolios. GET /v1/entities/{id}/trademarks returns the marks of owner records linked to the entity, and include_family=true adds GLEIF-reported subsidiaries. Neither is a complete-portfolio guarantee.
• Trademark events. USPTO timelines include the office’s e-mail notifications as their own office_action events; EUIPO timelines are publication events, not a lifecycle history. See Trademark Events.
• Restoration rules. The EU’s restitutio in integrum rule (eu_restitutio) is one of the restoration rules in GET /v1/deadline-rules; the reference listed only the others.
• Guides no longer state jurisdiction counts for deadline and opposition rules. GET /v1/deadline-rules and GET /v1/opposition-rules are the current lists.

​

October 1, 2026: a TTAB interlocutory order is no longer a proceeding’s decision

​

October 1, 2026: owner and entity names show accented characters

• owners[].name on trademark rows and trademark detail.
• name, name_original_script and aliases[].name on owners, and the names on /v1/owners/{id}/related.
• Entity names, member names and family names.
• Attorney client names, proceeding parties[].name and assignment parties[].name.
• trademark.owner_name on alerts and alert.created webhooks, and subject.name on party analytics.

​

October 1, 2026: MCP errors match REST; proceedings cursors are bound to their query

• A database statement timeout is timeout (504, retryable). It used to read “invalid or malformed ID”.
• A lost database connection, failover, or overloaded search cluster is service_unavailable (503, retryable).
• Any other server failure is internal_error with a reference_id. Database and search-engine messages no longer appear in tool results.
• Invalid arguments and unknown tool names return validation_error and not_found bodies instead of plain text. errors[] names each field.
• A preview_watch that runs out of time returns preview_timeout (504), as POST /v1/watches/preview does.
• get_account works for any key that can connect to MCP, not only keys with billing:read. Without billing:read it returns identity with plan: null.
• list_trademarks and list_proceedings with only blank filters ("", " ", []) return validation_error without running or charging.
• search_trademarks, list_trademarks and the party trademark tools reject an unknown status, status_stage or jurisdiction code instead of matching nothing.
• A JSON-RPC batch of more than 10 messages in one POST is rejected with JSON-RPC error -32600.
• A body that is not valid JSON or not a JSON-RPC message, or a request with malformed method parameters, returns a fixed JSON-RPC error with error.data.request_id, instead of the parser’s error text.

​

October 1, 2026: Benelux, Malta and OAPI member states resolve on /v1/jurisdictions

​

October 1, 2026: opposition, proceeding status and owner corrections

• A mark in its opposition window is no longer reported as opposed. USPTO marks with status code 686 (published for opposition), EUIPO marks with APPLICATION_PUBLISHED or START_OF_OPPOSITION_PERIOD, and INPI France marks in opposition_period no longer carry opposition_pending in status.challenges. An opposition that was actually filed still does (USPTO 774 and 801, EUIPO OPPOSITION_PENDING). A USPTO request for an extension of time to oppose (802) is now other_pending. status.stage is unchanged: pending_opposition means published for opposition or opposed, and the stage alone does not tell you which. Check status.challenges.
• Proceeding status is no longer inferred where the office did not report it. For EUIPO, CIPO and IP Australia, status is now an exact mapping of the office’s own label, still returned unchanged in status_raw.
  • EUIPO: CLOSED is other, not decided_rejected: the office reports that the case is closed but not who prevailed. Cases still running (RECEIVED, ADMISSIBILITY_CHECK, COOLING_OFF_PERIOD, and pending Board of Appeal or General Court cases) are pending. decision_date stays null for EUIPO proceedings.
  • CIPO: Active, Pending, Awaiting Decision and the appeal states are pending; Deemed Abandoned is decided_granted; Closed is other. proceeding_number is the office’s per-record sequence identifier (1, 2, …), not a Board docket number, and the API reference now says so.
  • IP Australia: Consent court order is settled, and Extension of time granted is other rather than decided_granted.
  • status.challenges follows: a CIPO or IP Australia mark whose opposition or cancellation is now pending carries the matching challenge, and one whose proceeding is no longer pending drops it.
• A live mark no longer loses its owners. An office update that arrived without owner data used to retire the current owners of a registered or pending mark, so it was served with no owner. A live mark now keeps its current owners in that case, and marks already affected get their owners back where our stored office data shows who the current owner is.

​

September 30, 2026: TTAB filing dates backfilled

​

September 30, 2026: party detail ETags change once

​

September 30, 2026: a trademark number in q returns that record

• A number in q returns one row per record, each shown as on its detail page, with an identifier_lookup warning in search_meta.warnings.
• A labelled international registration number, such as IR 1939139, returns one row for the international registration and its designations.
• A bare number returns the records it names. Records whose own number is the searched number come first, such as an international registration and any national record with that number. Designations that only carry the international registration number follow.
• A tm_ ID of a designation returns the designation, not its family.
• Text searches are unchanged.
• A pagination cursor issued before this change for a number in q is rejected with cursor_invalid. Start the search again.

​

September 30, 2026: USPTO assignments February to April 2026 complete

​

September 30, 2026: USPTO attorneys of record are representative

​

September 29, 2026: firms on Madrid families

• Grouped firm_id search matches every designation’s firm. When one attorney appears on several designations of an international registration under different firms, a grouped search filtered by firm_id now matches the family for any of those firms, not only the first, as expanded search already did. Existing families pick this up when they are next re-indexed.
• IR detail attorney order follows designation sequence. On an international registration with several designations, attorneys[] in trademark detail is ordered by the designation’s attorney sequence, not by designation office, so it matches the search index. Multi-designation IR details may list attorneys in a new order.
• Detail firm_name uses the firm’s display name. When the filing gives no firm name of its own, attorneys[].firm_name in trademark detail is now the firm’s display name (for example Smith & Jones, L.L.P.) instead of its upper-case matching key.

​

September 29, 2026: the primary image is always an image

​

September 29, 2026: one search request model: q, similarity, text filters and exclusions (breaking)

• similarity picks the channels q runs: identical, fuzzy, embedded, phonetic and lookalike. The default is identical,fuzzy,embedded,lookalike, and identical is always on. See Similarity.
• Text filters mark_text_is, mark_text_word, mark_text_starts_with, mark_text_ends_with, mark_text_contains and mark_text_pattern test the mark text. On GET, repeat the key for several values; commas are never split. On POST, send them under filters.mark_text. Alone they list marks in text order; with q they narrow the ranked results. See Text filters.
• Exclusions: mark_text_not_* for every text filter, plus owner_id_not, entity_id_not, entity_group_not and trademark_ids_not. On POST, send them under exclude.
• allow_partial (options.allow_partial on POST) returns the rows found so far when a search times out, with search_meta.complete: false.
• include=match_details adds match.details with the matching methods that fired and the ranking factors applied.

• match on every hit of a request with q or a text filter: { tier, via, terms }. tier is identical, near_identical, similar or related, a retrieval category rather than an edit distance. via lists the channels that found the hit. terms lists the text filter values it satisfied. See Match tiers.
• search_meta gains similarity_applied, order (relevance, mark_text_fit, filing_date or your sort), complete, incomplete_reason, identifier, ranking_version and deprecations.

• Default recall is wider. A q without similarity now also finds marks with a different first letter, look-alike characters and prefix phrases. embedded finds the term as a word, a phrase or the start of a word in a longer mark; a term in the middle of a word is not matched yet. Abbreviation matching and owner-name matching are removed from search; use Search Owners for owner names. search_meta.ranking_version is v12.
• Every search cursor restarts. Cursors issued before this release return 400 cursor_invalid. Cursors are now bound to the translated request, so an old-style request and its new-style equivalent share cursors.
• Scores survive sort. With q, relevance_score and match are on every hit whatever the sort. Under a sort the score keeps the status factor and drops the length factor.
• Text filters list in text order. Without q, a text filter orders marks equal to the value first, then marks starting with it, then shorter marks, then newer filings. The old match modes returned the newest filings first.
• A search that times out is a 503. A search that hits its time limit or loses a shard returns a retryable 503 unless allow_partial=true. Sorted searches too; they returned 400. The partial_results warning is removed.
• No quiet downgrades. A query too expensive to run returns 400 validation_error with errors[].code: too_complex, naming q or the text filter with the most values. It used to be retried with fewer strategies. The strategies_reduced warning is removed.
• New limits. q takes at most 22 words. contains, ends_with and wildcard-leading pattern values need 3 characters after folding, and one request takes at most 4 of them (400 too_big). Each such value takes one slot of the search concurrency budget.
• mark_text_not_contains ignores punctuation and spacing, like the other text filters, and takes repeated keys on GET.
• Explicit international_registrations=grouped on a request the grouped view can’t serve returns 400 unsupported_on_grouped. Leaving it unset keeps the expanded fallback and its warning.
• Skip warnings are per channel: <channel>_skipped with a channel field.

• Similarity watches take version: "v3", q, similarity and min_tier (identical, near_identical, similar or related; default related). Existing watches keep alerting exactly as before until their query is changed. See Watches.
• New watch queries use the new matching (added later on September 29). Create, bulk create, preview and an update that changes the query store it as version: "v3" whatever version you send: a plain { "version": "v2", "q": "acme" } gets the default channels and min_tier: "related". Only a query with strategies or min_match_tier is kept as a legacy watch. An update that sends the stored query back unchanged still changes nothing.
• Alerts gain match.tier, on REST and in webhooks. match.score is still the engine score for the watch query, not the 0 to 100 relevance_score.
• Watch preview and diagnostics report similarity_applied and min_tier.

​

September 28, 2026: party counts agree, Madrid designations show their serials, USPTO address and date fixes

• List and detail counts agree. GET /v1/attorneys, /v1/owners and /v1/firms list rows now read trademark_count and active_count from the same stats rows as the detail endpoints, not from the search index document. The monthly stats recompute now refreshes the search index for every party whose counts changed, and a repair pass is re-syncing attorney, firm and owner search documents (some attorneys and firms were missing from q search).
• Party detail ETags follow the stats. /v1/attorneys/{id}, /v1/owners/{id} and /v1/firms/{id} ETags change when the stats are recomputed; /v1/entities/{id} folds its live counts in. A client revalidating a cached body gets 200 with current counts instead of 304.
• Counting grain is in the spec. Every party stats field now says what it counts: trademark_count and active_count count marks (a Madrid IR and its designations once); registered_count, pending_count, expired_count, cancelled_count, abandoned_count, the rates and avg_prosecution_days count office records, so the status counts can sum to more than trademark_count. jurisdiction_count counts offices.
• Madrid designations carry their own numbers. coverage.territories[] on grouped IR rows (search, party trademark lists, Retrieve Trademark, Batch Trademarks) adds the designation record’s office_code, application_number and registration_number, so a US designation shows its 79-series serial on the grouped row. Pass international_registrations=expanded for one row per designation; the party trademark list pages now document it.
• IR detail lists its designations’ attorneys. Retrieve Trademark for a Madrid IR (grain: mark) now rolls up attorneys[] from its designations, as it already did for owners and classifications. Each attorney on such a row carries territory_codes, the designations whose record names them. IR-parent ETags change once.
• Attorneys show their office. Attorney list and detail rows carry source_office_code. Attorney records are per office: the same person appears once per office they file at.
• firm_id matches the firm of record. The firm_id filter and facet on trademark lists match the firm of record on the filing when known, else the attorney’s current firm, the same firm detail rows show. Index documents built before this change pick it up on the next index rebuild. USPTO filings stored before April 2026 are getting their firm of record from the correspondence address line.
• USPTO addresses. USPTO attorney addresses are parsed into lines, city, region, postal_code and country_code (a trailing “United States” line no longer lands in lines), and USPTO attorneys get country_code: "US", so GET /v1/attorneys?country_code=US returns them. Rows whose office gave no country stay null and are excluded from a country_code filter. USPTO owners now carry their street lines in address.lines. New and updated marks get these from this release; stored rows are repaired in place without webhooks or alerts.
• TTAB filing dates. US proceedings now take filed_date from the USPTO TTAB feed; before, only about 2% had one, so filed_date_* filters, sort=filed_date and filed_year undercounted. Historical rows are being backfilled; until the warning on the proceedings pages is removed, do not rely on TTAB date filters.
• Assignments. The assignment pages state their scope: USPTO only, refreshed daily, with the USPTO’s 6 to 10 week recordation lag. Assignments recorded February to April 2026 are being reloaded.
• USPTO event codes in the catalogue. GET /v1/event-types?office_code=US lists about 1,000 USPTO prosecution history codes with the event_type each maps to. SUNA (notice of acceptance of a statement of use) is now always approval; the mailed form was typed response_filed.
• Clearer office_code error. office_code on GET /v1/trademarks still returns 400; the message now names offices (one or more codes) and office (one code).
• Docs. Per-tier include values (full_goods_services on lists, office_extensions on detail and batch), webhook examples on payload_version: 2 with real status values, a portfolios walkthrough for status-change notifications, current plan limits, and ETag/If-None-Match change detection on List Deadline Rules.

​

September 28, 2026: OpenAPI nullability checked against live responses

​

September 28, 2026: one primary media item; document fields on media

• media[].is_primary marks exactly one item whenever primary_image_url is set: the item that URL points at. A detail with several images and no office-flagged primary used to show every item as is_primary: false while primary_image_url still pointed at one of them; the two now come from one rule. When primary_image_url is null, no item is primary.
• media[].document_kind, media[].official_date, media[].page_count are added (additive, nullable) for a document item: document_kind is the same kind GET /v1/trademarks/{id}/documents serves for that document (Signa’s classification of the office’s document type), and official_date and page_count are the office’s document date and page count, null when the office published none. All three are null for images. TypeScript SDK types regenerated.

​

September 28, 2026: Madrid family status.challenges is the union across designations

​

September 28, 2026: Entity trademarks list scopes like the entity_id filter

• No member-owner cap. The endpoint no longer answers 422 entity_too_large with reason: member_owners_too_large for an entity with more than 10,000 member owners; it lists. The only remaining 422 is family_graph_too_large from include_family=true.
• Resource semantics are unchanged. A missing entity is still 404, a merged one 410, and include_family=true still walks the entity’s own subtree. The MCP tool get_entity_trademarks follows the same scope.

​

September 28, 2026: filter-only order on expanded rows, mixed on the record grain

• Filter-only requests served one row per record are newest first. A request without q or sort that is answered with expanded rows (international_registrations=expanded, or a grouped fallback such as aggregations or an unsupported sort) now returns the newest filings first (-filing_date), as documented and as the grouped view already did. Cursors minted by such requests before this release may no longer continue; start the walk again.
• status_primary=mixed and status_stage=mixed are grouped-view filters. A request served one row per record that carries them is now a 400 validation_error (unsupported_on_record_grain, naming what forced the record grain) instead of an empty page.
• debug_timing is no longer documented on GET /v1/trademarks. It never changed a response; it is still accepted and ignored.
• TypeScript SDK 0.16.0 drops ranking_profile and options.include_profile from the search types.

​

September 28, 2026: q takes a list of exact terms; q_any is replaced (breaking)

• The list form. On GET, write the whole value as a JSON array of strings: q=["limber","bimber"]. On POST, send an array in query or q: {"query": ["limber", "bimber"]}. The response is the same as q_any gave: every mark that is an exact match for any term, each hit carrying matched_terms, and search_meta.match reads exact. See Several exact terms.
• One term is unchanged. A string q works exactly as before. It is always literal text: no operators, no comma splitting. Only a value that parses in full as a JSON array of strings is a list, so [RE]BUILD and [1,2] are still searched as written.
• A list runs match=exact. It is the default for a list, and sending it is allowed. Any other match, or strategies, with a list is a 400 validation_error.
• 100 terms per list (q_any took 200), each up to 200 characters. Long lists go by POST: a GET query string over 2 KB is rejected before it reaches the API.
• q_any is replaced. A request that sends q_any gets a 400 validation_error whose message names the list form; move the terms into q unchanged. The request is not billed and never runs as a filter-only search. Cursors minted by q_any requests may no longer continue; start the walk again.
• Pricing is unchanged. One page of a list search costs the same as one page of any search, regardless of how many terms it carries.
• TypeScript SDK 0.15.0 types q as string | string[] on trademarks.list() and trademarks.search() and removes q_any. SDK 0.14.0 sends q_any, so upgrade before relying on the list form.

​

September 28, 2026: mixed_script search warning

​

September 27, 2026: Provenance release follow-ups

• CIPO status labels. Signa used to join CIPO’s status and its internal description into one status.raw.label (for example Registration published - Registered). The label is now CIPO’s internal description alone (Registered), the same text a record without a status code carries. status.raw.code is unchanged, and List Status Codes still serves null labels for CIPO.
• EUIPO event labels. On EUIPO trademark events whose text Signa composed from several fields (bulletin publications, oppositions, cancellations, appeals, seniorities, decisions), raw is null and the text stays in description. EUIPO’s own recordal kinds, such as Proprietor - Total transfers, are still served as raw.label.
• IPOS event labels. The filing and registration events Signa adds to IPOS trademarks (Application filed, Registration procedure completed) use Signa’s wording, so raw is null and the text stays in description. IPOS’s own event entries are unchanged.
• INPI event codes. Signa used to join INPI fields into one event code, such as Inscription: Changement d'adresse or Transaction: Correction. raw now carries the fields alone: a recordal is {"code": "Inscription", "label": "Changement d'adresse"} and a weekly transaction is {"code": null, "label": "Correction"}. Events from INPI’s status history are unchanged.
• OpenAPI nullability. Enums documented as nullable now list null among their values, and derived.next_deadline is declared as a DeadlineRow or null. Responses are unchanged; a strict OpenAPI validator now accepts the null values the API already returned.
• Event types. List Event Types catalogues IP Australia (AU) and WIPO (WO) codes today. Other offices return an empty list.

​

September 27, 2026: The provenance release (breaking)

​

Trademark rows (search, lists, portfolios, screening, batch, detail)

• Status. status.source is now status.basis (office, event_derived, dispatch_derived, computed). status.raw_code and status.raw_label are now status.raw: {code, label} (or null). The label is the office’s verbatim text only: null when the office publishes none, or when the stored text was the code itself or wording Signa wrote. Decode codes with the new List Status Codes.
• Dates. expiry_date_basis and renewal_due_date_basis are removed; top-level dates are office-published only. New last_renewal_date, the last renewal the office recorded (USPTO, CIPO and OEPM today). In every jurisdiction the rulebook treats the renewal cycle it paid, and every earlier cycle, as paid, so an early-renewed registration no longer lists the paid cycle as due. last_renewal_date on a POST /v1/deadlines/compute item works the same way (it used to be read for Canada only). A paid cycle is not a missed one either: urgency=missed on GET /v1/deadlines and portfolio deadlines, and include_missed: true on POST /v1/deadlines/compute, no longer list a cycle before the office-stated expiry, the cycle a recorded renewal paid, or the restoration window such a cycle would open. include_missed used to return that paid history.
• An IR’s expiry_date is the expiry WIPO published on its designations. Known limitation: the search index does not hold it on the IR’s own record yet, so expiry_date_* does not match the IR’s own record and sort=expiry_date orders it with rows that have no office expiry. The next index rebuild fixes this. Also known: a renewal WIPO publishes on the designations moves the IR’s expiry_date without raising a trademark.updated event or alert for the IR’s own id (Watches).
• derived on every row, search hits included: ruleset_version (an rs_ content hash, was a date), as_of_date, expiry_date, deadlines {supported, reason, unsupported_rules, items[]}, next_deadline and opposition_window. The detail’s deadlines_supported, deadlines_unsupported_reason and deadlines_unsupported_rules move into derived.deadlines, and the deadline array into derived.deadlines.items.
• Opposition window. The top-level opposition_window on search rows is removed. derived.opposition_window is always present and two-state: {supported: true, rule_id, trigger_event, publication_date, window_opens, window_closes, close_adjustment, office_time_zone, common_extension} or {supported: false, reason, rule_id} with no null date keys. rule_version is removed.
• Deadline rows, everywhere a deadline appears (the derived block, GET /v1/deadlines, portfolio deadlines, POST /v1/deadlines/compute): grace_expiry is grace_expiry_date, recurring and optional are is_recurring and is_optional, name and description are removed, and new occurrence_key, due_date_adjustment, grace_expiry_adjustment, holiday_calendar and consequence_if_missed appear on every row. occurrence_key identifies one occurrence within one trademark across reads: rule_id:<cycle>, or rule_id:t<term>-<n> when the record has no statutory anchor date or the row is anchored on an office-stated expiry. The calendar event UID namespaces it by trademark: tm_<uuid>:<occurrence_key>@signa.so. Madrid rules report jurisdiction_code: "WO", and a POST /v1/deadlines/compute item sent as WIPO echoes WO.
• Office record. source_primary_id is replaced by office_record_id (the office’s own id; null only when Signa composed the key: an IR’s own record and its WIPO-feed, Finnish and Polish designation records; other national-office records of a designation keep the office’s id) and office_url.
• IR numbers lose Signa’s WO prefix in registration_number ("WO921642" is now "921642"), and the registration_number filter matches the unprefixed number.
• Owners. owners[].entity_id is the resolved entity or null; owners[].entity_id_type is removed; owners[].entity_type is now owners[].legal_form. Detail owners gain is_current.
• Attorneys (detail): attorneys[].firm_id and firm_name are the firm of record on the filing, falling back to the attorney’s current firm (they used to be the current firm). The firm_id filter and facet still match the attorney’s current firm, so about 5% of records can be returned for a different firm than their detail shows, until the next index rebuild.
• Addresses have one shape everywhere (owners, attorneys, assignment parties): {lines[], city, region, postal_code, country_code, formatted}. state is region, lines are verbatim, and components appear only when the office supplied them.
• Register. The detail’s us_register is replaced by register {type, acquired_distinctiveness, is_incontestable, standard_characters_claimed} (or null), on every row and for every office that states one.
• Grain. New grain: "mark" | "record". coverage, source_records and owners_mixed appear only on Madrid IR family rows (they were null on others). Coverage territories are {territory_code, status {primary, stage}, trademark {id, href}, office_url, ...} (they were territory, primary, stage and trademark_id), and the IR’s own WO record is no longer listed as a territory.
• The row-level office_updated_at is removed (the detail keeps it under provenance, which gains snapshot_date).
• territory_matches[].basis is matched_via_kind.
• classifications[].class_status_raw is classifications[].status_raw {code, label}.
• design_codes[] are {system, code, edition} (were code_system, code_value), with system one of vienna, us_design_search, other.
• filing_bases[].nice_class_number is filing_bases[].nice_class.
• classifications[].scope (as_filed) appears only on IR family rows.
• classifications[].nice_class can be null (a class the office stated without a Nice number).
• The detail’s jurisdiction_code can be null, as on the row.

​

Search and filters

• Removed filters (now a 400): renewal_due_before (use renewal_due_date_lt), us_register_type (use register_type, which works for any office register), opposition_closes_before and opposition_closes_after (use opposition_closes_lte and opposition_closes_gte). This applies to GET and POST /v1/trademarks and to the owner, attorney, firm and entity trademark lists.
• Grouped per-leg filters. On the default grouped view, the office, route, filing, registration and expiry date and registration number filters stay grouped, alone or together: they must hold on the same record, and they match the leg shown in coverage.territories[] for each territory. When a territory has both a WIPO-feed and a national-feed record, the one Signa does not show (listed in source_records) does not match.
• search_meta.fallback_reason is removed. A grouped request served one row per record now carries an expanded_fallback entry in search_meta.warnings[] with affected_filters or affected_option.
• search_meta.index_generation is new. Cursors are bound to the index generation, so a cursor minted before this release is rejected with 400 cursor_invalid: restart pagination. The same applies after any future index rebuild.
• New result_window_reached warning (severity: info) in search_meta.warnings[]: the last page of a relevance-ranked or sorted walk that the 10,000-row window ended while more rows match. A walk that ran out of matches never carries it.
• entity_id and entity_group with an owner id in entity form (ent_<owner-uuid>) return an empty page. Filter a single owner with owner_id.
• entity_id and entity_group on trademark search no longer return 422 entity_too_large for an entity with more than 10,000 member owners; they match the entity directly. entity_group keeps its family-walk bound, and the other entity surfaces keep the member cap (errors).
• opposition_status and opposition_closes_* match only while the mark is at a stage it can be opposed at (the gate behind stage_not_opposable); they used to match at any stage.
• If Signa cannot load a result page’s stored data (owner entity links, record facts, IR family facts), a trademark search or list request now fails with a retryable 503 service_unavailable and Retry-After: 5 instead of serving a degraded page. An owner-lookup failure used to serve owners[].entity_id: null and show owners that are normally hidden.

​

Other endpoints

• Batch (POST /v1/trademarks/batch): identifiers name their office with office_code (office is now a 400). data answers every submitted item in input order, and a repeated id repeats.
• Events (GET /v1/trademarks/{id}/events): rows are object: "trademark_event" with their own hst_ ids (were event and evt_); raw_code and raw_label are raw {code, label}; nice_class_number is nice_class; sequence_no is sequence_number; description is null unless it adds office text to raw.label. The org feed GET /v1/events keeps object: "event".
• USPTO event types. A USPTO notice of suit (NOSU) is event_type: "litigation" (was office_action), so it no longer matches event_type=office_action and no longer raises office_action.issued. Attorney and domestic-representative appointments, revocations and withdrawals are representative_changed (were address_change); a representative’s own address change stays address_change. Labels naming the USPTO’s examining attorney, which the old rule also filed as address_change, take the type their label maps to (for example other or correction). Stored history is retyped after the release, with no webhook or alert.
• Entities. entity_id_type is removed. Entities are materialized entities only: GET /v1/entities/{id} (and /trademarks, /family) with an owner id in entity form is a 404, linked owner or not; a merged entity stays 410. GET /v1/entities no longer lists unlinked owners, and members[].link is never null.
• Owners, attorneys, firms. Owner entity_id (list and detail) is the linked entity or null, and entity_id_type is removed. Stats earliest_filing and latest_filing are earliest_filing_date and latest_filing_date (sort values are unchanged). aliases[].source_office is source_office_code. address is the one address shape.
• legal_form on every party. entity_type is legal_form on owners (list and detail), attorney clients (GET /v1/attorneys/{id}/clients), entities (list and detail) and entity members[], as on trademark owners[]. The GET /v1/owners and GET /v1/entities filter entity_type is legal_form (the old name is a 400 that names it).
• Proceedings (GET /v1/proceedings/{id}): trademark.serial_number and trademarks[].serial_number are application_number.
• Event types (GET /v1/event-types): raw_code and raw_label are raw {code, label}, as on a trademark event. The label follows the verbatim-label rule, so WIPO rows (whose catalogue labels are Signa’s descriptions) have label: null. The office filter is office_code, as on GET /v1/status-codes; office and any other unknown parameter are a 400.
• Assignments. reel_no, frame_no, release_of_reel_no and release_of_frame_no end in _number; new office_code. Parties: nationality is country_code (ISO alpha-2, null when the office named no country) and address is the one address shape. Properties: serial_no, registration_no, intl_reg_no and mark_name are application_number, registration_number, ir_number and mark_text.
• Deadlines. unsupported_marks[].unsupported_reason is reason on GET /v1/deadlines and portfolio deadlines. Compute items: unsupported_reason is reason. Opposition compute items fold unsupported_reason into reason. Reconcile computed.unsupported_reason is computed.reason. GET /v1/deadline-rules reports Madrid rules as jurisdiction_code: "WO" (was WIPO); its jurisdiction filter still accepts WIPO as an alias.
• Calendar (GET /v1/portfolios/{id}/deadlines.ics): event UIDs are tm_<id>:<occurrence_key>@signa.so. A file downloaded after the release adds every event again beside the ones imported earlier (delete those once); afterwards, re-importing updates an event whose due date was corrected instead of duplicating it.
• Offices (GET /v1/offices, /v1/offices/{code}): coverage and coverage_computed_at are data_completeness and data_completeness_computed_at. data_completeness.expiry_date counts office-stated expiries only.
• Citations: disposition_as_of is disposition_at.
• Goods and services suggest: accepted_terms[].harmonised is is_harmonised.
• Office analytics: earliest_filing and latest_filing are earliest_filing_date and latest_filing_date.
• Screening: screening_id values change once (the receipt now binds the served index generation) and again after each index rebuild.
• ETags change format. Every cached validator gets one 200, then 304s resume.
• Watches: a watch filtering on expiryDate or renewalDueDate now matches office-published values, like the search filters. New watches cannot target an owner id in entity form; use filters.ownerId. Existing watches that did are migrated to filters.ownerId, or to the entity the owner has since been linked into, and keep evaluating the same marks.
• New: List Status Codes (GET /v1/status-codes?office_code=US; unknown query parameters are a 400).

​

Webhooks and GET /v1/events (payload_version 2)

• office_action.issued v2 replaces the flat event_date, event_code, event_label, scope, status_after_event, nice_class_number, description, source_identifier and sequence_no with trademark_event, the same row GET /v1/trademarks/{id}/events returns.
• Change field names in v2 (trademark.status_changed changed_fields and changes, alert.created alert.event.diff[].path, and REST alert event.diff[].path): source_primary_id is office_record_id, status_source is status_basis, and expiry_date_basis and renewal_due_date_basis are no longer published.
• Change values in v2 follow the row: status_basis uses the status.basis vocabulary; an expiry_date or renewal_due_date side that is not office-stated is null, and a change between two computed values is omitted; status_raw_label follows the verbatim-label rule; registration_number has no WO prefix.
• No alert is raised for a change whose every changed field is one the row does not publish (a Signa-computed date moving, or a basis change that stays non-office), so an alert never arrives with an empty diff.
• Both versions: on events emitted from the release on, data.occurred_at is ISO 8601 UTC with milliseconds (2026-09-26T22:23:21.191Z), as GET /v1/events serves it. It used to carry Postgres text (2026-09-26 22:23:21.191924+00), which strict ISO parsers rejected. Retries and redeliveries of events emitted before the release keep the old text.

​

MCP

​

Upgrading

1. Read expiry as expiry_date ?? derived.expiry_date, and deadlines from derived.deadlines.items.
2. Rename the filters above, and batch office to office_code.
3. Treat owners[].entity_id as nullable, and use owner_id for unlinked owners.
4. Restart any paginated walk that spans the release.
5. Branch webhook handlers on payload_version.
6. Upgrade to @signa-so/sdk 0.14.0 (TypeScript SDK). Its types follow every change above. The old filter names are not translated: the API answers them with a 400 naming the replacement, and list()’s POST fallback throws a SignaError that names it. toArray() never returns a short array silently: it throws SignaTruncatedError past its 10,000-item default cap, and also when the API ended a relevance-ranked or sorted search at its 10,000-row window while more rows match (the last page’s result_window_reached warning).

​

September 24, 2026: Declined deadline rules and uncomputed marks are now listed

• POST /v1/deadlines/compute: every item carries unsupported_rules, an array of { rule_id, reason, missing_field, consequence_if_missed }. It is [] when nothing was declined, and [] when supported is false, because unsupported_reason already covers every rule.
• GET /v1/trademarks/{id}, POST /v1/trademarks/batch and the MCP get_trademark tool: the derived block carries deadlines_unsupported_rules in the same shape, next to deadlines_supported and deadlines_unsupported_reason.
• GET /v1/deadlines and GET /v1/portfolios/{id}/deadlines: the list envelope carries unsupported_marks, one entry per mark in the requested portfolio or trademark that was not computed at all (supported: false) or was computed only in part (supported: true with unsupported_rules). Marks with a status that ends every obligation, such as abandoned or withdrawn, are not listed. Entries use the same supported, unsupported_reason and unsupported_rules fields as a compute item. The list covers the whole scope, not just the page, ignores the type, urgency and due_before filters, and is sorted by trademark_id. It is reported on the first page (a request without cursor) and is null on continuation pages.

​

September 24, 2026: Older Nordic registrations without a filing date get deadlines

​

September 24, 2026: Monitoring and reconcile on every plan; internal actions leave Get Credit Pricing

​

September 24, 2026: offices and filing_route keep Madrid results grouped

​

September 24, 2026: Canadian and Brazilian date rolls, six-month Madrid renewal windows, and new deadline fields

• Canada: grace_expiry rolls to the next day the office is open (Trademarks Act s. 66(1)), reported in grace_expiry_adjustment. due_date never rolls: it is the end of the term. window_opens on the office-anchored ladder no longer falls before the registration date (Regulations s. 159(a)).
• Brazil: due_date and grace_expiry roll to the next business day (Lei 9.784/99 art. 66 § 1º, applied by art. 69), reported in due_date_adjustment and grace_expiry_adjustment.
• Madrid designations in CH, FR, AU, FI, PL, BR, IN, KR and CN: the renewal window_opens is six months before the due date, the period the International Bureau accepts a renewal in (Common Regulations Rule 30(1)(b)). It was 12 months. due_date and grace_expiry do not change.
• India: the 7-year or 10-year first term is chosen by the Indian filing date, not the convention priority date. A convention application filed on or after 15 September 2003 with an earlier priority date now gets the 10-year term (filed 1 October 2003, priority 1 May 2003: due 1 May 2013, was 1 May 2010). The priority date is still the date the term is counted from.

​

September 24, 2026: q_any checks up to 200 exact terms in one request

​

September 24, 2026: One-character searches on owner, attorney and firm trademark lists

​

September 24, 2026: Watches accept one- and two-character CJK keywords

​

September 24, 2026: Mixed-alphabet and accented queries match like the index

​

September 24, 2026: Screening and compare no longer reject brackets and parentheses

​

September 23, 2026: Long name searches return 400, not 503

​

September 23, 2026: Abandoned searches stop, and partial pages say so

​

September 23, 2026: Relevance search pages to 10,000 rows on both views

​

September 23, 2026: entity_count and owner_count aggregations

​

September 23, 2026: match=exact ignores punctuation and spacing

​

September 23, 2026: Single CJK characters are valid search queries

​

September 23, 2026: Brackets and parentheses in q no longer return 400

​

September 23, 2026: Watch preview evaluates the watch query

​

September 23, 2026: strategies now runs only the strategies you pass

​

September 23, 2026: Aggregation counts now respect your filters

​

September 23, 2026: pre-reform Nordic records without a registration date are declined

​

September 23, 2026: close_adjustment gains month_end_overflow

​

September 23, 2026: an absolute statutory ceiling is never rolled past

​

September 23, 2026: the Australian Christmas close-down is no longer projected

​

September 23, 2026: EUIPO closure days are pinned back to 2023

​

September 23, 2026: dates outside a calendar’s pinned coverage are rolled again

​

September 21, 2026: Proceedings now link both sides, with trademark_role (breaking)

• contested: the proceeding targets this mark (the opposed application, the registration under cancellation, the appealed application).
• asserted: the opposer or petitioner pleaded this mark as a prior right.

​

September 21, 2026: One row per TTAB opposition on US marks

​

September 18, 2026: TTAB proceedings, and how to read them

• GET /v1/trademarks/{id}/proceedings lists the proceedings a mark is party to, each with parties[].
• GET /v1/proceedings searches across marks. One filter is required: trademark_id, proceeding_type, status, q (a party name), party_owner_id, party_entity_id, party_role, office_code, contested_class or a filed_date / decision_date range. Aggregations cover outcome, party_role, nice_class, office_code and filed_year.
• GET /v1/proceedings/{id} returns one proceeding with its parties and the mark it belongs to.

• A proceeding is attached to the mark it was filed against. An opposer’s own marks do not list the oppositions that opposer filed. To profile an opposer, search by party instead: GET /v1/proceedings?q=<name> or party_owner_id=<own_…> (correction, October 1, 2026: party_owner_id returns no results until parties are linked to owners; use q). Decided cases from the Reading Room are attached to every party’s marks.
• Many filed_date values are null. We trust only the filing date TTABVUE states for the proceeding; the bulk feed’s dates proved unreliable, so rows we have not yet confirmed carry no date and no duration_days. The default sort is -filed_date, so those rows come last.
• Parties are names. parties[].name is the name as filed, and owner_id is set only where it resolved to a known owner.
• There is no filing-by-filing docket, and no events or webhooks fire on a proceeding change. Poll the list, or watch the mark’s status.challenges for opposition_pending and cancellation_pending.

​

September 14, 2026: Consistent trademark detail validators

​

September 14, 2026: Renewed marks stop showing the paid renewal cycle on US §8/§9 and MX renewals

• US Section 8 plus Section 9 (combined_renewal_and_use). A mark registered in 2016 and renewed through 2036 still listed the satisfied 2026 cycle, in grace and apparently actionable, for the six months after that date.
• Mexico’s combined renewal and declaration of use (mx_renewal, also combined_renewal_and_use, national route). A renewed Mexican registration lost its paid cycle the same way. Madrid designations of Mexico renew centrally at WIPO under renewal and were never affected.

​

September 14, 2026: Docs and spec alignment: rule catalogs join Filing & docketing, alpha labels, monitoring status reference

​

September 11, 2026: Reconcile becomes a docket audit (verdict_detail)

​

September 11, 2026: Fee endpoints accept platform office codes

​

September 6, 2026: Portfolios are public

​

September 5, 2026: Auth hardening, plan_gated, prefixed watch filters

​

September 4, 2026: nine deadline rules relabelled, and consequence_if_missed is an open string

​

September 3, 2026: prosecution deadlines are served outside calendar coverage

• moved: the office calendar was consulted and rolled the date forward off a day the office is shut.
• unchanged: the calendar was consulted and the date was already an open day.
• not_checked: no calendar verdict stands behind the date. Either the date falls outside the calendar’s pinned coverage, the rule ships without a roll rule, or the office stated the date itself (a stated deadline is published exactly as stated and never rolled). Treat it as the raw statutory anniversary and confirm before relying on the exact day.
• null: no date was produced at all.

​

September 3, 2026: France, Finland and Poland Madrid designations get opposition windows

​

September 3, 2026: holiday calendars now stop where their evidence stops

• EU opposition closes for 2027 and later are no longer rolled. A window whose close lands on a weekend or a 2027 Spanish feast is now served on the raw statutory date. Example: an EU application published 30 November 2026 closes 28 February 2027 rather than 1 March 2027.
• EU dates before 2025 are outside the calendar. An EU office-action response deadline computed from a 2024 mailing is no longer rolled against the unpinned 2024 block. Superseded the same day: this originally returned insufficient_facts with reason holiday_calendar_out_of_coverage. It now returns the un-rolled statutory date with due_date_adjustment: "not_checked". See the entry above.

​

September 3, 2026: close_adjustment on every opposition window

​

September 3, 2026: opposition rule catalog reports both eras

​

September 3, 2026: rule corrections (CN, PH, CH, CA, DE, MX)

​

September 3, 2026: maintenance deadline corrections (EU, MX, NO, CA)

​

September 3, 2026: China (CNIPA) deadlines and opposition windows

​

September 3, 2026: Benelux opposition windows before 1 October 2013 corrected

​

September 3, 2026: German Madrid designations get an opposition window

​

September 3, 2026: Swiss Madrid opposition windows close up to 30 days earlier

​

September 3, 2026: Norway Madrid opposition, and a publication-date guard for every Madrid rule

​

September 3, 2026: EU restitutio, Canada’s transitional renewal window, India’s priority-dated term, and WIPO closure days

​

September 3, 2026: Mexican OPPOSITION windows follow the same month-overflow rule, and the overflow is now reported

​

September 3, 2026: Mexican deadlines now roll, month-overflow ends in the next month, and Madrid designations renew on the international registration

​

September 3, 2026: Australian renewal grace periods roll onto the next open day

​

September 3, 2026: renewal dates roll on closed office days in Norway, France and Iceland, and on BOIP’s own closing days in the Benelux

​

September 3, 2026: EUIPO Article 2 days now extend time limits; consequence_if_missed vocabulary fixed

​

September 3, 2026: Philippines, India and Iceland business-day calendars re-sourced

​

September 3, 2026: Korea (KIPO) deadline and opposition rules

​

September 3, 2026: Türkiye dates now roll, pre-2018 renewal windows and the 2017 opposition straddle corrected

​

September 3, 2026: Danish renewal dates on office closing days now roll

​

September 2, 2026: Philippines Renewal DAU window opens six months earlier

​

September 2, 2026: Philippines Madrid designations get their own DAU anchors

​

September 2, 2026: Swedish publication and expiry dates corrected (PRV connector)

​

September 2, 2026: Canada (CIPO) opposition extension benchmark before December 2023

• derived.opposition_window.common_extension for a CA direct-route window that closes before 1 December 2023 now reads months: 4 (was 2) with notes naming the 2019 notice and the 9-month cooling-off figure.
• A window closing on or after 1 December 2023 keeps months: 2; its notes are rewritten (they no longer claim the window is “otherwise non-extendable” - the 7-month cooling-off extension exists) and name the straddle: a window that opened before 1 December 2023 and closes on or after it may have been extended under either figure depending on when the request was received.
• GET /v1/opposition-rules continues to show the current (2-month) tier for ca_opposition; the rule’s citations gain the superseded 2019 notice and CIPO’s own side-by-side changes page, both pinned from the Wayback Machine because the office has removed them.
• ca_opposition_madrid is untouched: Trademarks Regulations s. 125 caps the Protocol-application extension at 4 months in every era.

​

September 2, 2026: MX oppositions before 30 August 2016 are no longer served

​

September 2, 2026: India (CGPDTM) deadline and opposition rules

​

September 2, 2026: Türkiye (TÜRKPATENT) deadline and opposition rules

​

September 2, 2026: Japan (JPO) deadline and opposition rules

​

September 2, 2026: opposition window opening day corrected (Benelux, Finland, Norway, Sweden)

​

September 2, 2026: German renewal dates corrected for applications pending on 14 January 2019

​

September 2, 2026: French renewal grace end corrected (moves later)

​

September 2, 2026: office calendar corrections

• EUIPO: 8 December 2025 and 2026 no longer roll; those are Article 2 ordinary-post-only days, not Article 1 office closures. Reindex EU opposition documents.
• CIPO: weekend substitutes for 24 June and 30 September now roll on the following Monday. Those two need no reindex before the first affected 2028 opposition cohort. Separately, the 17–19 September 2025 office closure now rolls through the weekend to 22 September, so CA documents published 17 to 19 July 2025 carry an opposition close date up to five days early until CA is reindexed. Opposition status is unaffected: those windows are already closed.
• IPOS: 11 August 2025 and 20 March 2026 no longer roll; the excluded days 1–16 May 2024 roll to 17 May, and 14 October 2025 rolls to 15 October. Reindex affected Singapore opposition documents.
• IP Australia: Canberra Day, Saturday and Sunday ANZAC Day substitutes, and the standing 25 December–1 January close-down now roll. For example, 9 March 2026 rolls to 10 March, 27 April to 28 April, and 29 December to 4 January 2027. Reindex Australian opposition documents.
• IPI: the conservative nationwide calendar now excludes canton-specific days, including 2 January, Good Friday, Easter Monday, Whit Monday, 1 May, 26 December. The governing party or representative canton is not available to the engine, so deadlines are never moved later based on the wrong canton. Reindex Swiss opposition documents.
• DKPTO: 15 May and 28–30 December 2026 now roll as enumerated office closures. Reindex is not currently needed because Signa has no DK office documents; revisit when DK ingestion lands.
• INPI France: 15 May 2026 now rolls to 18 May under the Director General’s closure decision. Reindex French opposition documents.
• DPMA: the one-off Berlin holiday on 8 May 2025 now rolls to 9 May. No reindex is required for the weekly weekday publication cohort.

​

September 2, 2026: Era-aware opposition citations

• Australia, direct and Madrid, published before 2013-04-15 (3 months): Trade Marks Regulations 1995 reg 22.9 item 2 for a direct application and the 2012 compilation’s reg 17A.29(2)(b)(i) for an international registration, in place of the current reg 5.6(1) / reg 17A.33(1) “2 months”.
• India, published before 2013-07-08 (3 months): Trade Marks Rules 2002 r. 47(1), in place of s. 21(1) “four months”.
• Thailand, published before 2016-07-28 (90 days): s. 35 paragraph 1 of the Trademark Act B.E. 2534 as in force before Act (No. 3) B.E. 2559, in place of the current s. 35 paragraph 1 “sixty days”.
• Türkiye, direct and Madrid, published before 2017-01-10 (3 months): the repealed Decree-Law 556 art. 35/1, and WIPO Information Notice No. 19/2014 for a designation, in place of SMK 6769 art. 18/1 “iki ay” for a direct application and the WIPO Madrid Member Profile (“two months from the date of publication of the international registration”) for a designation.
• Vietnam, published before 2026-04-01 (5 months): Law 07/2022/QH15, in place of Law 131/2025/QH15, which states only the three-month period.

​

September 2, 2026: Vietnamese opposition windows corrected (3 months since 1 April 2026)

​

September 2, 2026: Brazilian and Mexican renewal deadlines

​

September 2, 2026: Icelandic renewal dates corrected

​

September 2, 2026: Office rule reference data provenance

​

September 2, 2026: The events feed is documented (beta)

​

September 2, 2026: Alert diffs use public field names (breaking, beta)

​

September 2, 2026: Office dates and your docket reference on events

"portfolios": [{ "id": "ptf_9aB2xY", "external_ref": "MATTER-4471" }]

​

September 2, 2026: Webhook subscriptions, portfolio scope, and diff field names

​

September 2, 2026: Richer goods/services validation evidence

​

September 2, 2026: Goods/services catalog validation

​

September 2, 2026: Entity lists and suggest answer 503 when OpenSearch is unavailable

​

September 2, 2026: Saved searches removed

​

September 2, 2026: Swedish renewal dates corrected

​

September 1, 2026: Office-action webhook events

​

September 1, 2026: Trademark status webhooks and portfolio-scoped endpoints

​

September 1, 2026: Webhook event envelope (BREAKING)

​

September 1, 2026: Forward replay on GET /v1/events

curl "https://api.signa.so/v1/events?sort=id&after=evt_3D7rZ9&limit=100" \
  -H "Authorization: Bearer $SIGNA_API_KEY"

​

September 1, 2026: Examiner citations

​

September 1, 2026: Every rule has a stable id

​

September 1, 2026: Prosecution deadlines on /v1/deadlines/compute

• computed, a modelled rule produced or retired a date
• stated, no modelled rule exists but the office stated the deadline itself
• facts_required, a rule exists and is verified, but you must supply the trigger
• unsupported, no rule is modelled

​

August 31, 2026: Computed data moves under derived

const today = new Date().toISOString().slice(0, 10);
const overdue = d.due_date < today;
const inGrace = overdue && d.grace_expiry !== null && d.grace_expiry >= today;

​

August 30, 2026: Deadline engine statutory corrections

• This can add rows to marks you already fetch. A cancelled GB mark that returned no deadlines yesterday can return a restoration row today. Client code that assumed a dead mark implies an empty array should be checked.
• Rows can also disappear for expired marks without a reported expiry. The engine will not invent a lapse it cannot corroborate: an expired mark with no office-stated expiry date is served only the cycle whose window is currently open, never a restoration row derived from an assumed earlier miss. Clients alerting on deadlines[] shrinking should expect this.

• Denmark: the 2019 regime split is keyed on the registration date, not the filing date (Lov 1533/2018 §8 stk. 3). Marks filed before 2019-01-01 but registered after it were anchored up to a year off.
• Mexico: the 2020 regime split is keyed on the filing date, not the grant date (LFPPI Transitorio DÉCIMO). Applications in prosecution when the LFPPI entered into force on 2020-11-05 stay on the old filing-anchored term.
• Philippines: the third-year declaration of use window opens at the filing date and runs to the third anniversary of filing (RA 8293 §124.2). It was previously computed as a single day.
• Thailand: publications before 2016-07-28 get the 90-day opposition window that was in force at the time. The 60-day window applies only from the 2016 amendment forward.

​

July 25, 2026: Jurisdiction protection scope

• Result counts grow. A country-scoped filter picks up the regional rights that protect it. On production data, jurisdictions=FR roughly doubles once EU trade marks are counted. Countries with no live national office but active EU coverage (for example DE) go from a handful of Madrid hits to full EUTM coverage.
• territory_match=direct restores the old behavior. Pass it to match only literal territory legs, byte-for-byte the pre-July-2026 result set. The default is territory_match=protection. Requesting a regional code (EU) stays strict on search: it matches EUTMs and IRs designating the EUIPO, not member-state national marks.
• Why results grew is now explained. Under the default protection mode, each hit returned with a jurisdictions filter carries territory_matches[], mapping the requested code to the territory it matched on and the basis (direct leg or regional_membership). The field is absent under territory_match=direct. search_meta.territory_match echoes the mode that ran.
• Suggest and image search grow too. GET /v1/trademarks/suggest and POST /v1/trademarks/search/image apply the same protection-scope expansion and accept territory_match. Suggest now also matches Madrid designations of a requested territory (an international registration designating France is suggested under jurisdictions=FR), and image search echoes the applied mode as search_meta.territory_match.
• Member-country codes are newly accepted. Benelux member states (BE, LU, NL) and OAPI member states (for example SN) had no jurisdiction row of their own and previously returned 400. They are now valid jurisdictions values, so jurisdictions=BE selects Benelux and EU rights that protect Belgium.
• Saved searches were removed on September 2, 2026. Saved searches replay under the new semantics automatically. A stored search with jurisdictions=FR is re-executed against the current matcher, so it now returns EU trade marks it did not before, with no change on your side. If you need a saved search to keep the old literal-leg behavior, re-save it with territory_match=direct.
• Breaking for pagination. Because the query shape of a jurisdiction-filtered search changed, pagination cursors minted before this release on such a query now return 400 cursor_invalid. Clients holding a stale cursor must restart pagination from the first page.
• During the rolling deploy, expect a brief mixed window. While the release rolls out, requests may land on either old or new instances, so a jurisdiction-filtered query can alternate between the old and new result sets, and territory_match may return 400 from a not-yet-updated instance. Stale jurisdiction-filtered cursors invalidate as above. The window closes once every instance is on the new release; retry the request if you hit it.

• New verdict value. GET /v1/screening verdicts are now high_risk / caution / needs_review / clear. needs_review is a would-be clear that could not be confirmed because a requested territory’s register is dark or stale. Handle it as “we could not rule this out”, not as a weaker clear. Found conflicts still band high or medium exactly as before, observed risk is never suppressed.
• Why this is deliberate. Before this change, screening a common brand in a class scoped to a territory whose national register was not yet connected could return clear with zero conflicts, even though real national marks existed and were simply invisible to us. Returning clear there is a false negative on a clearance product. We would rather tell you the corpus was incomplete than imply a name is safe.
• A new coverage block on the screening response reports which registers gated the verdict (offices axis in ST.3 codes, territories axis in jurisdiction codes) and a complete_for_clear boolean. See Screen a Name.
• Check a Listing gets the same protection-scope expansion, and an incomplete requested register forces a would-be clear to caution (the listing verdict enum is unchanged).
• Screening responses are no longer client-cacheable. They are served Cache-Control: private, no-store. Re-run a screen rather than replaying a stored response.
• screening_id values changed at this epoch. The identifier now folds the coverage inputs that can flip a verdict, so ids minted before this release do not correspond to ids minted after. Do not treat a pre-release screening_id as stable across this boundary.
• Watches are unchanged. Monitoring keeps office-based scoping and does not apply the protection-scope expansion, so a watch scoped to a country still watches that country’s office only (a DE watch does not surface EU trade marks). See Create Watch.

​

July 14, 2026

• Compare (beta): POST /v1/compare, its TypeScript SDK resource, and its developer guide complete the public-facing Intelligence surface alongside Screening. Compare scores one candidate against up to 10 selected conflicts.