USPTO Trademark Gazette Search & Weekly Watch avatar

USPTO Trademark Gazette Search & Weekly Watch

Pricing

from $53.60 / 1,000 confirmed gazette event deltas

Go to Apify Store
USPTO Trademark Gazette Search & Weekly Watch

USPTO Trademark Gazette Search & Weekly Watch

Search the latest USPTO Trademark Official Gazette for current opposition, registration, renewal, cancellation, and correction records. Start with a fast snapshot, then schedule a filtered weekly watch for new events.

Pricing

from $53.60 / 1,000 confirmed gazette event deltas

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

™️ USPTO Trademark Gazette Search & Weekly Watch

Get current trademark records from the latest USPTO Trademark Official Gazette — including marks, owners, classes and official event types, each linked to its public TMOG case page. Turn on watch mode only when you want a private baseline followed by new weekly events. Public, logged-out; no API key.

Output is one gazette_record row per result; billing is pay-per-event, the value event being one confirmed gazette event delta (a $0.02 start fee per run, then $0.08 per confirmed gazette event delta). Source: tm-eog-service.uspto.gov, tmog.uspto.gov, www.uspto.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out.

Who it's for

Trademark counsel watching publication/registration records within the 30-day opposition window, brand-protection teams monitoring terms and classes, and IP data teams ingesting dated Gazette records.

📊 Sample Output

USPTO Trademark Gazette Search & Weekly Watch sample output — a table of real confirmed gazette event delta rows (issue_date, event_type, section_heading, serial_number) from run d0LlJQOiLTMaD7Ta7 on build 0.2.6

Real rows from run d0LlJQOiLTMaD7Ta7 on build 0.2.6 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

issue_dateevent_typesection_headingserial_numbercomposite_idcomposite_key
2026-09-15PUBLICATION_FOR_OPPOSITIONPublished for Opposition79434441USPTO:SN794344412026-09-15|PUBLICATION_FOR_OPPOSITION|SN:79434441
2026-09-15PUBLICATION_FOR_OPPOSITIONPublished for Opposition79434442USPTO:SN794344422026-09-15|PUBLICATION_FOR_OPPOSITION|SN:79434442
2026-09-15PUBLICATION_FOR_OPPOSITIONPublished for Opposition98913715USPTO:SN989137152026-09-15|PUBLICATION_FOR_OPPOSITION|SN:98913715
2026-09-15PUBLICATION_FOR_OPPOSITIONPublished for Opposition99322423USPTO:SN993224232026-09-15|PUBLICATION_FOR_OPPOSITION|SN:99322423
2026-09-15PUBLICATION_FOR_OPPOSITIONPublished for Opposition99347912USPTO:SN993479122026-09-15|PUBLICATION_FOR_OPPOSITION|SN:99347912
2026-09-15PUBLICATION_FOR_OPPOSITIONPublished for Opposition99348017USPTO:SN993480172026-09-15|PUBLICATION_FOR_OPPOSITION|SN:99348017
2026-09-15PUBLICATION_FOR_OPPOSITIONPublished for Opposition99352404USPTO:SN993524042026-09-15|PUBLICATION_FOR_OPPOSITION|SN:99352404
2026-09-15PUBLICATION_FOR_OPPOSITIONPublished for Opposition99420383USPTO:SN994203832026-09-15|PUBLICATION_FOR_OPPOSITION|SN:99420383

The run finished with the status message: CAPPED: delivered 25 of 36 matches

✅ What you get

One of three record types discriminated by record_type: trademark_delta (watch signal), gazette_record (snapshot), or source_receipt (never billed).

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_type (string) — e.g. gazette_record
  • office — e.g. USPTO
  • issue_date — e.g. 2026-09-15
  • issue_number — e.g. 38
  • event_type — e.g. PUBLICATION_FOR_OPPOSITION
  • section_heading — e.g. Published for Opposition
  • serial_number — e.g. 79434441
  • registration_number — null in every sample row
  • composite_id — e.g. USPTO:SN79434441
  • composite_key — e.g. 2026-09-15|PUBLICATION_FOR_OPPOSITION|SN:79434441
  • mark_text — e.g. AI OS
  • mark_type — e.g. UNKNOWN
  • owner_name — e.g. IMPLEMENT AI LTD 85 Great Portland Street, First Floor London W1W 7LT GB UNITED
  • owner_address — null in every sample row
  • international_classes — e.g. [35, 41, 42]
  • goods_services — e.g. Business consultancy and advisory services relating to the adoption, deployment
  • filing_date — e.g. 2025-08-26
  • publication_date — e.g. 2026-09-15
  • registration_date — null in every sample row
  • page_number — null in every sample row
  • parse_warnings — null in every sample row
  • source_url (string) — e.g. https://tmog.uspto.gov/search/single-case-view?serialNumber=79434441&issueDate=2
  • observed_at (string) — e.g. 2026-09-17T18:16:58Z
  • source_hash — e.g. 579477d2b793fbc2ad06336f04e55ec6bc1e1d2e06bc10b35fa527a484497342

What each record contains

  • gazette_record — a current-issue snapshot record (when watchMode = false): the mark, owner, status, Nice classes, event type, and issue date as printed in the Gazette.
  • trademark_delta — a confirmed new Gazette event on a watched mark (watch mode). delta_type is the event type (or CORRECTED_ENTRY); carries before / after, changed_fields, and an office-scoped composite_id (USPTO:SN… / USPTO:RN…).
  • source_receipt — stored outside the paid dataset in the RUN_RECEIPT key-value record, never billed: terminal state, issues processed, API records checked, byte/request counters, and any backlog.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"watchMode": false,
"markTextKeywords": [
"AI"
],
"eventTypes": [
"PUBLICATION_FOR_OPPOSITION"
],
"maxCatchupIssues": 1,
"maxItems": 25
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 0 × $0.08 trademark_delta + 1 × $0.10 gazette_issue_check = $0.12 on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

2. A smaller, narrowed run

{
"watchMode": false,
"markTextKeywords": [
"AI"
],
"eventTypes": [
"PUBLICATION_FOR_OPPOSITION"
],
"maxCatchupIssues": 1,
"maxItems": 5
}

Caps the run at 5 rows; same billing shape as the sample run above.

3. Watch mode on a schedule

{
"watchMode": true,
"markTextKeywords": [
"AI"
],
"eventTypes": [
"PUBLICATION_FOR_OPPOSITION"
],
"maxCatchupIssues": 1,
"maxItems": 25
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.08 each.

🧾 JSON sample record

One real record from run d0LlJQOiLTMaD7Ta7, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "gazette_record",
"schema_version": "1.0",
"office": "USPTO",
"issue_date": "2026-09-15",
"issue_number": 38,
"event_type": "PUBLICATION_FOR_OPPOSITION",
"section_heading": "Published for Opposition",
"serial_number": "79434441",
"registration_number": null,
"composite_id": "USPTO:SN79434441",
"composite_key": "2026-09-15|PUBLICATION_FOR_OPPOSITION|SN:79434441",
"mark_text": "AI OS",
"mark_type": "UNKNOWN",
"owner_name": "IMPLEMENT AI LTD 85 Great Portland Street, First Floor London W1W 7LT GB UNITED KINGDOM 24 PRIVATE LIMITED COMPANY",
"owner_address": null,
"international_classes": [
35,
41,
42
],
"goods_services": "Business consultancy and advisory services relating to the adoption, deployment and scaling of artificial intelligence; business management consultancy in the field of digital transformation; compilation, analysis and interpretation of busi",
"filing_date": "2025-08-26",
"publication_date": "2026-09-15",
"registration_date": null,
"page_number": null,
"parse_warnings": [],
"source_url": "https://tmog.uspto.gov/search/single-case-view?serialNumber=79434441&issueDate=2026-09-15",
"observed_at": "2026-09-17T18:16:58Z",
"source_hash": "579477d2b793fbc2ad06336f04e55ec6bc1e1d2e06bc10b35fa527a484497342"
}

🔧 How it works

Transport. Requests go through Apify residential proxy. robots.txt is read first and a disallowed path is never fetched.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each confirmed gazette event delta is charged at the moment it is pushed (trademark_delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

First run and later runs — read this first

Two modes:

  • Snapshot (watchMode: false, the runtime and form default): returns the current Gazette issue's matching records right away as gazette_record rows. Omitting watchMode also selects snapshot, so {} does not silently seed an empty watch. Billed one gazette_issue_check for the issue processed — the snapshot records themselves are not billed per-record. Use it to see the data now.
  • Watch (watchMode: true): the first run seeds a private baseline and emits zero deltas (it establishes what already exists so it does not alert you to history). Later Tuesday issues produce only new matching events as trademark_delta — this is the change feed. maxCatchupIssues (1–3) bounds how much backlog each run processes.

Only an explicitly requested watch run seeds rather than alerting; point that watch at a weekly schedule and the deltas start with the next issue.

Source, scope and limits

Public / logged-out official USPTO TMOG search service only; robots honoured; no login, API key, CAPTCHA or paywall defeating. The Actor walks every result page in your requested filter scope before calling an issue complete, while returning only your requested maxItems. owner_name preserves USPTO's public current-owner display text, which can include an address; owner_address remains null on this source path. Identity is office + serial/registration number, using official publication reasons only — legal outcomes are never inferred. This is not TSDR live status, legal docketing, clearance, ownership verification, or legal advice. The Gazette is weekly and event-oriented — absence proves nothing. Design-only marks may have null mark text. Catch-up is capped at 3 issues/run. Blocks, incomplete pagination and shape drift fail loud, never as a clean empty.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with input 3 above (watch_mode: true), and pick a cadence:

  • Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
  • Weekly — 0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Confirmed Gazette event delta (trademark_delta)$0.08$0.07$0.06$0.05
Gazette issue processed (gazette_issue_check)$0.10$0.09$0.08$0.07

Worked at the live Free-tier price (watch mode, one delta per change):

  • 8 confirmed gazette event deltas: $0.02 start + 8 × $0.08 = $0.66
  • 25 confirmed gazette event deltas: $0.02 start + 25 × $0.08 = $2.02
  • 5000 confirmed gazette event deltas: $0.02 start + 5000 × $0.08 = $400.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 512 MB.

Yield on the sample run: CAPPED: delivered 25 of 36 matches. maxItems is a hard ceiling on what is delivered and billed, never a target.

This actor reads public, logged-out pages and feeds published by tm-eog-service.uspto.gov, tmog.uspto.gov, www.uspto.gov. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (tm-eog-service.uspto.gov, tmog.uspto.gov, www.uspto.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxItems (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: What does watch mode remember between runs?
A: A private baseline of source-native record ids in a named key-value store. Each later run diffs the live source against it and emits only changes.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other IP and trademark watches actors?
A: Same output shape and billing model; this one covers tm-eog-service.uspto.gov, tmog.uspto.gov, www.uspto.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (maxItems) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • First watch run shows no deltas → expected: it seeds the baseline; changes appear from the second run.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.