# USPTO Trademark Gazette and Status Watch (`thirdwatch/uspto-trademark-watch`) Actor

Compare trademark Gazette notices and status records for known serial numbers. Keep issue dates, publication reasons and international classes with each event.

- **URL**: https://apify.com/thirdwatch/uspto-trademark-watch.md
- **Developed by:** [Thirdwatch](https://apify.com/thirdwatch) (community)
- **Categories:** Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.75 / 1,000 trademark publication or serial-status events

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## USPTO Trademark Gazette and Status Watch

> Compare trademark Gazette notices and status records for known serial numbers. Keep issue dates, publication reasons and international classes with each event.

### What you get

A brand analyst can route a publication-for-opposition notice separately from a registration or cancellation.

### Output fields

The default example produces these top-level fields. Nested records can be expanded in JSON or selected during export.

| Field | Meaning |
| --- | --- |
| `eventId` | Identifier for this observed event. Use it when deduplicating downstream. |
| `event` | Change or observation category assigned to this row. |
| `serialNumber` | USPTO serial number identifying the trademark application. |
| `issueDate` | Date or time reported for the relevant source publication or submission. |
| `sourceReason` | Publication or status reason supplied by the source. |
| `internationalClasses` | Nice classification numbers reported for the trademark. |
| `mark` | Mark reported or calculated for this record. |
| `source` | Publisher, feed or source named by the observation. |
| `sourceMode` | Input source or marketplace mode for the resulting record. |
| `sourceUrl` | Source or dataset location associated with the row. |

### Example output

Selected fields from a verified run on supplied illustrative data. The JSON below is an excerpt from one row.

```json
{
  "event": "published_for_opposition",
  "serialNumber": "50000156",
  "issueDate": "2026-10-27",
  "sourceReason": "Published for Opposition",
  "internationalClasses": [
    9,
    42
  ],
  "source": "USPTO Trademark Official Gazette",
  "sourceUrl": "https://tmog.uspto.gov/"
}
```

### Input parameters

In the input form, switch to JSON, paste the input below and start the actor. Open the run’s dataset to inspect or export the result.

Select a Gazette issue or provide authorized known-serial status records. Preserve the source issue date and class. A live status lookup requires the entitled USPTO key where specified.

<details>
<summary>Copy the complete, runnable input</summary>

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

</details>

| Parameter | Use | Meaning |
| --- | --- | --- |
| `gazetteIssues` | Optional / mode-specific | Specify date (YYYY-MM-DD or latest), optional integer internationalClasses, offset and maxRecords per issue. Up to four weekly issues. |
| `serialWatches` | Optional / mode-specific | Each entry requires an eight-digit serial and either an authorized TSDR XML snapshot or a USPTO key for live retrieval. |
| `previousState` | Optional / mode-specific | Copy the previous successful NEXT_BASELINE to suppress repeat events. |
| `usptoApiKey` | Optional / mode-specific | Required only for live known-serial lookup. Public weekly Gazette issue searches use no key. Enter this as a credential in the input form. |

### Use cases and integration

For a repeat run, save the input as an Apify Task. Keep the approved scope and pass the newer observation on subsequent runs. For an API integration, submit JSON to [this actor’s run endpoint](https://api.apify.com/v2/acts/thirdwatch~uspto-trademark-watch/runs). On success, read `defaultDatasetId` from the run and export its items as JSON or CSV.

### Limitations

Coverage follows weekly USPTO Gazette issues and authorized known-serial lookups. A missing notice does not establish the status of a mark.

[Official Gazette](https://www.uspto.gov/learning-and-resources/official-gazette/trademark-official-gazette-tmog) · [USPTO TSDR API access](https://www.uspto.gov/trademarks/apply/check-status-view-documents/trademark-bulk-data) · [USPTO API guide](https://www.uspto.gov/sites/default/files/documents/tm-enterprise-api-user-guide-v2.pdf)

### Compared to alternatives

A serial-number lookup gives the current record. Compare Gazette issues when you need a published notice, its reason and its class on a particular issue date. Related options: [dev00/uspto-trademark-api](https://apify.com/dev00/uspto-trademark-api) and [memo23/uspto-trademark-scraper](https://apify.com/memo23/uspto-trademark-scraper).

### FAQ

**Is the first notice an application filing?**

Use the source reason and issue date. Gazette publication, registration, renewal and cancellation have different meanings.

Last verified: 2026-11. The verified sample run returned 4 dataset rows. [Thirdwatch](https://thirdwatch.dev)

# Actor input Schema

## `gazetteIssues` (type: `array`):

Specify date (YYYY-MM-DD or latest), optional integer internationalClasses, offset and maxRecords per issue. Up to four weekly issues.

## `serialWatches` (type: `array`):

Each entry requires an eight-digit serial and either an authorized TSDR XML snapshot or a USPTO key for live retrieval.

## `previousState` (type: `object`):

Copy the previous successful NEXT_BASELINE to suppress repeat events.

## `usptoApiKey` (type: `string`):

Required only for live known-serial lookup. Public weekly Gazette issue searches use no key.

## Actor input object example

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

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "gazetteIssues": [
        {
            "date": "2026-11-03",
            "internationalClasses": [
                9
            ],
            "maxRecords": 2
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("thirdwatch/uspto-trademark-watch").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "gazetteIssues": [{
            "date": "2026-11-03",
            "internationalClasses": [9],
            "maxRecords": 2,
        }] }

# Run the Actor and wait for it to finish
run = client.actor("thirdwatch/uspto-trademark-watch").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "gazetteIssues": [
    {
      "date": "2026-11-03",
      "internationalClasses": [
        9
      ],
      "maxRecords": 2
    }
  ]
}' |
apify call thirdwatch/uspto-trademark-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thirdwatch/uspto-trademark-watch"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/BGI12AKfP1uLZFjBx/builds/yk9ZOx3GlGpK9fnb1/openapi.json
