# UK IPO Trade Mark Journal Change Signals (`starshaped_bullsnake/uk-ipo-trade-mark-journal-change-signals`) Actor

Track new and changed matters in the official UK IPO Trade Marks Journal.

- **URL**: https://apify.com/starshaped\_bullsnake/uk-ipo-trade-mark-journal-change-signals.md
- **Developed by:** [Starshape Tools](https://apify.com/starshaped_bullsnake) (community)
- **Categories:** Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 uk trade mark journal signals

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## UK IPO Trade Mark Journal Change Signals

Monitors newly published and changed matters in the official UK IPO Trade Marks Journal for IP-monitoring teams. It does no similarity, conflict, infringement or legal-risk inference.

Official source: [UK IPO Trade Marks Journal](https://www.ipo.gov.uk/t-tmj.htm), its weekly XML data file and publication metadata. The XML is streaming-parsed to avoid loading the roughly 200MB journal into memory. The publication describes UK applications and international registrations accepted in the prior week and the printed journal identifies amendments/corrections, cancelled publications, goods/services restrictions and international protection conferred. Crown copyright information is reused under the Open Government Licence v3.0: contains public sector information licensed under the OGL v3.0. Persistent normalized storage, derived signals and redistribution are permitted with that attribution.

Signal types are `NEW_ACCEPTED_APPLICATION`, `APPLICATION_AMENDED`, `PUBLICATION_CANCELLED`, `GOODS_SERVICES_RESTRICTED`, and `INTERNATIONAL_PROTECTION_CONFERRED`. Identity is the official trade mark number; a journal event is keyed by trade mark number + journal date + event type. Names never determine identity.

`{"mode":"sample","maxItems":100}` is the deterministic demonstration mode used by the example run. It creates representative before/after journal events and passes them through the same production normalize, diff and filtering logic. It does not fetch the official journal, open the production named key-value store, or read/write the production baseline. Live mode uses the official source and persistent snapshot.

The first live run is a zero-signal baseline. An identical live rerun emits zero. Processing is fetch → streaming parse → normalize → validate → previous snapshot → diff → Dataset → summary → compressed snapshot commit; failures before the final commit retain the prior snapshot. `maxItems` only caps Dataset output and never truncates the stored live snapshot. Other inputs are `signalTypes`, `tradeMarkNumbers`, `niceClasses`, `applicantNames`, `keywords` (literal filter), and `baselineOnly`.

Schedule weekly after publication; no real-time freshness is promised. Known limitations: UK IPO can alter XML vocabulary or temporarily challenge automated clients; image-only marks may have null `markText`; source corrections are reported, not interpreted. The complete weekly snapshot is thousands of records and compressed storage/network parsing dominate resource use.

# Actor input Schema

## `mode` (type: `string`):

Sample demonstrates signals without reading or changing the live snapshot.

## `signalTypes` (type: `array`):

Optional output signal types.

## `tradeMarkNumbers` (type: `array`):

Official number filter.

## `niceClasses` (type: `array`):

Nice class filter.

## `applicantNames` (type: `array`):

Literal applicant filter.

## `keywords` (type: `array`):

Literal keyword filter.

## `baselineOnly` (type: `boolean`):

Store live baseline without signals.

## `maxItems` (type: `integer`):

Caps Dataset output only; never truncates a live snapshot.

## Actor input object example

```json
{
  "mode": "live",
  "baselineOnly": false,
  "maxItems": 1000
}
```

# Actor output Schema

## `OUTPUT` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("starshaped_bullsnake/uk-ipo-trade-mark-journal-change-signals").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("starshaped_bullsnake/uk-ipo-trade-mark-journal-change-signals").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 '{}' |
apify call starshaped_bullsnake/uk-ipo-trade-mark-journal-change-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,starshaped_bullsnake/uk-ipo-trade-mark-journal-change-signals"
        }
    }
}
```

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/wKRtgZr0FMHESeR0B/builds/t4ZFgcPqWD4SIjflt/openapi.json