Skip to main content
Thirdwatchthirdwatch
Companies & leads

How to Track USPTO Trademark Gazette Notices by Issue Date

Track USPTO Gazette notices by issue, class and serial number. Distinguish publication for opposition from registration and resume a partial review safely.

Editorial illustration for companies & leads
· Updated · 7 min read · 1,522 words
View the Apify scraper →

The USPTO Trademark Gazette and Status Watch separates what appeared in a weekly issue from what the office currently says about a serial. Choose a dated issue and class, preserve the publication reason, and record how much of the issue you covered. In the November 3 example, two class 9 notices had different meanings. PIRLEX appeared for opposition and LYCANSCOUT had a registration issued. Both matter to a brand researcher, but they belong in different review queues.

Why track a trademark notice by issue date and serial?

A useful weekly brief tells its reader which official event occurred and where to check it. A headline saying “two new trademarks” leaves a product team guessing whether someone filed applications, reached the opposition stage, or received registrations. The Gazette publishes on Tuesdays and includes more than one kind of notice. A filing that first comes to your attention on Tuesday can have a much earlier application date. Keep the issue date under its own label. USPTO guide to the Trademark Official Gazette

The size of an issue changes how a team reviews it. In a verified search of international class 9, the October 27, 2026 issue reported 3,389 matches and the November 3 issue reported 3,586. A two-record check for each date produced four notices. That was enough to verify the distinction between event types. A report describing all class 9 activity for either week would need the rest of the pages. Enter those dates and class 9 in the official Gazette to inspect the underlying issues. USPTO Gazette issue search

Assign the serial to the research record first and the mark text to a display field second. One October 27 result, serial 50000156, belonged to classes 9 and 42 and had no text in the returned mark field. It still had a valid serial, issue date and publication reason. A filter that keeps only named text marks silently discards this kind of record. A watch limited to class 9 also needs to retain all classes reported on a matched notice.

Which source fits the question?

The Gazette answers a publication question and TSDR answers a known-case status question. A third option is to collect and compare multiple weekly observations in a repeatable watch. The choice depends on the evidence you need to hand to the next reviewer.

Method Good fit Evidence to retain Work to repeat
Browse a dated Gazette issue One mark or a small set of notices Issue date, serial, source reason Locate entries and record how far you reviewed
Open a known serial in TSDR Current case status or official case documents Serial, status, effective date and source record Verify the latest case details when acting on them
Run a dated Gazette watch A recurring class or brand-research brief Event ID, source reason, coverage and next baseline Continue unfinished pages and assign records to reviewers

A team can use both sources on the same case. Suppose the weekly brief includes an opposition publication from last month and a colleague asks what happened since. Preserve the original notice as historical evidence. Add a new status observation from TSDR alongside it. Replacing the old row with today’s status obscures what the Gazette actually said that week. USPTO status and document lookup

How do I track weekly USPTO notices by class and serial?

A repeatable review has four parts. Fix the scope, save the returned notices, read the coverage, and carry the successful baseline forward. For a small pilot, two records per issue are enough to inspect the shape of the data and confirm that the event labels are useful to your reviewers.

How do I choose the two issues?

A fixed date makes a review reproducible. This input asks for two records from class 9 in each of two successive issues. The integer in internationalClasses identifies the international class. The per-issue maximum limits how much each search returns.

{
  "gazetteIssues": [
    {"date": "2026-10-27", "internationalClasses": [9], "maxRecords": 2},
    {"date": "2026-11-03", "internationalClasses": [9], "maxRecords": 2}
  ]
}

Use latest to discover the current issue in a recurring workflow, then retain the resolved date when you continue paging. If a new Tuesday issue appears while your team is still reviewing the older one, an offset alone cannot identify which issue to resume. A dated review also lets a colleague reproduce a disputed result after the newest issue changes.

How do I keep the source reason when exporting?

The default dataset contains the notice rows for a successful run. Once you have access to the actor, the following Python example runs the dated input saved above as issues.json. The exported lines retain the official reason alongside the normalized field used for routing.

import json
import os
from pathlib import Path
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
config = json.loads(Path("issues.json").read_text())
run = client.actor("thirdwatch/uspto-trademark-watch").call(run_input=config)
assert run["status"] == "SUCCEEDED"
notices = client.dataset(run["defaultDatasetId"]).list_items().items
for notice in notices:
    print(notice["serialNumber"], notice["issueDate"], notice["sourceReason"])

Store the serial as a string. A serial is an identifier even when it consists entirely of digits. Use sourceReason when quoting the meaning of a notice to an internal reviewer. Use event for automation that separates opposition publications from registrations. Keep eventId as the downstream duplicate key if an export is retried. Apify dataset documentation

Where do I resume an unfinished issue?

The run’s default key-value store holds an ISSUE_COVERAGE record with one entry per requested issue. For November 3, the example reports two observed matches and a next offset of two. Use the same class filter with that offset. A larger page size on a follow-up run can advance the review further.

store = client.key_value_store(run["defaultKeyValueStoreId"])
coverage = store.get_record("ISSUE_COVERAGE")["value"]
remaining = [
    {"date": c["issueDate"], "internationalClasses": c["internationalClasses"],
     "offset": c["nextOffset"], "maxRecords": 25}
    for c in coverage if c["nextOffset"] is not None
]

Two separate counts belong in a handoff. The source’s totalMatches describes the query. The Actor’s observed describes the page it actually read. If your team reviewed only those two November records, say exactly that in the brief. A count of source matches cannot tell you how many records your system saved, which records an analyst has reviewed, or how many marks ultimately received registrations.

What carries over to the next run?

NEXT_BASELINE remembers Gazette events and previously observed serial statuses. Pass it as previousState together with your next set of issues. The following code continues both unfinished dates. Save the new baseline only after you have also saved the new rows and checked the run status.

baseline = store.get_record("NEXT_BASELINE")["value"]
if remaining:
    next_run = client.actor("thirdwatch/uspto-trademark-watch").call(
        run_input={"gazetteIssues": remaining, "previousState": baseline}
    )
    assert next_run["status"] == "SUCCEEDED"

A lost acknowledgement can send the same dataset page to your spreadsheet twice. Treat each eventId as an upsert key and keep one row per event. For a separate status watch, add serialWatches with the eight-digit serial and provide the required TSDR credential through the secret field. The first successful status observation provides a baseline. The official USPTO explains how access to the TSDR API works. USPTO TSDR bulk data access

What do two notices from the same issue look like?

The following selected fields came from the November 3 Gazette search. They describe two records from the same class and date. Their source reasons justify different actions in a research report.

[
  {"serialNumber":"50000593","issueDate":"2026-11-03","mark":"PIRLEX","event":"published_for_opposition","sourceReason":"Published for Opposition","internationalClasses":[9]},
  {"serialNumber":"50001031","issueDate":"2026-11-03","mark":"LYCANSCOUT","event":"registration_issued","sourceReason":"Trademark Registration Issued","internationalClasses":[9]}
]

Route the first record to the group reviewing opposition publications and the second to the group tracking registrations. Keep both in the issue archive. A registration notice does not reveal the full prosecution history, and an opposition publication by itself does not establish the case’s current status. Use the serial to open the official case when the next decision requires those facts.

What commonly goes wrong in a weekly watch?

The most frequent mistake is treating an absence as an event. A serial can disappear from a weekly result because the issue changed, the requested class changed, or the reviewer collected only one page. A cancellation requires an explicit source notice or case record. The Actor produces publication events from records it observed and reports how much of each query it covered.

A second mistake is collapsing all dates into a field named “date.” The issue date belongs to the publication notice, while the effective date in a TSDR status record belongs to a different observation. Keep both when your application combines them. A third mistake is forwarding case names without the serials or the link to the official service. Brand teams can save considerable review time by preserving those references in the first export.

Which related workflows help with official notices?

The Federal Register notices workflow shows how another government publisher labels source events. The compliance alert guide covers recurring review, and the Federal Register Python guide discusses exporting official records. Those sources have different jurisdictions and notice types. For broader collection patterns, see the business data guide and the Thirdwatch blog.

Frequently asked questions

Does publication for opposition mean the trademark has been registered?

Publication for opposition identifies the reason a mark appeared in an issue. Registration is a separate event with its own evidence. Record the Gazette reason and issue date as given. Open the serial in TSDR when your question concerns the current status of the application.

How can I tell whether I finished a class?

Read ISSUE_COVERAGE for the issue and class you requested. The next offset identifies where to continue, and a null next offset indicates the end of that query. Retain the issue date itself when you continue a search that initially used latest.

Can I follow a trademark whose mark text is missing?

The eight-digit serial provides a stable starting point even when a Gazette entry lacks a text mark. Keep the original serial and review the official entry for its drawing or description. Treat an absent text field as missing information instead of supplying an invented label.

When does the monitoring workflow require my USPTO API key?

The weekly Gazette search in the worked example uses the public issue service. A live status lookup for a known serial requires a TSDR key authorized for that service. Supply it through the designated secret field and keep it out of shared examples and exported datasets.

Related