WIPO UDRP Domain Decision Watch avatar

WIPO UDRP Domain Decision Watch

Pricing

from $67.00 / 1,000 case deltas

Go to Apify Store
WIPO UDRP Domain Decision Watch

WIPO UDRP Domain Decision Watch

Snapshot or watch WIPO UDRP domain-dispute decisions. Snapshot returns recent decisions; watch mode reports new decisions only.

Pricing

from $67.00 / 1,000 case 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

™️ WIPO UDRP Domain Decision Watch

Follow WIPO UDRP domain-name disputes as they move — complainant, respondent, the domains at issue, and the outcome (Case active → Transfer, Cancellation, Complaint denied or Terminated) — as a change feed keyed on the source-native case number. Public, logged-out WIPO decision index; no API key, login, cookie or CAPTCHA.

Output is one case_record row per result; billing is pay-per-event, the value event being one case delta (a $0.02 start fee per run, then $0.10 per case delta plus one $0.10 source check per run that reads the source). Source: www.wipo.int.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

Who it's for

Domain and brand-protection teams, IP counsel tracking cybersquatting outcomes, and registrars or data teams that need a dated change feed of UDRP decisions.

📊 Sample Output

WIPO UDRP Domain Decision Watch sample output — a table of real case delta rows (case_number, complainant, respondent, domain_names) from run s4vgo9Lmo6XObQRof on build 0.1.21

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

case_numbercomplainantrespondentdomain_namesdecisiondecision_available
D2026-4000Associated Newspapers Limited DMG Media Limited-["elizafashion.com"]TerminatedFalse
D2026-3815Union des Associations Européennes de Football (“UEFA”)-["uefachampionsleague-hr.com"]TerminatedFalse
D2026-3820SODEXO-["sodexo.rest"]TerminatedFalse
D2026-3839Association des Centres Distributeurs E. Leclerc – A.C.D. Lec-["leclerc.vip"]TerminatedFalse
D2026-3845C Digital Technologies Limited-["casumocasinouk.org"]TerminatedFalse
D2026-3869Leung Ting, trading as the International WingTsun Association ('IWTA')-["iwta.com"]TerminatedFalse
D2026-3906GERFLOR-["gersflor.net"]TerminatedFalse
D2026-3917Loomis Sayles & Company LP-["loomissaylesdanfuss.com"]TerminatedFalse

The run finished with the status message: PARTIAL: emitted 25 item(s); PREVIEW: snapshot output is capped at 25 record(s); 9 further record(s) withheld. Use watch mode for the full change feed.

✅ What you get

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_key (string/null) — e.g. wipo:D2026-4000
  • case_number — e.g. D2026-4000
  • complainant — e.g. Associated Newspapers Limited DMG Media Limited
  • respondent — e.g. -
  • domain_names — e.g. ["elizafashion.com"]
  • decision — e.g. Terminated
  • decision_url — null in every sample row
  • decision_available — e.g. False
  • scope_note — e.g. case index only; the index carries no dates and the decision text is not opened
  • record_type (string) — e.g. case_record
  • delta_type (string/null) — null in every sample row

What each record contains

A case_record (snapshot) or case-delta (watch): case number, complainant, respondent, domain name(s), and the decision/outcome — the columns the WIPO index publishes. In watch mode each delta is NEW / CHANGED / REMOVED with before / after and changed_fields. Terminated or still-active cases with no decision link are kept and flagged decision_available: false, not dropped.

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)

{
"year": 2026,
"blocks": 3,
"watch_mode": false,
"max_items": 40
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.10 case-delta = $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

{
"year": 2026,
"blocks": 3,
"watch_mode": false,
"max_items": 5
}

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

3. Watch mode on a schedule

{
"year": 2026,
"blocks": 3,
"watch_mode": true,
"max_items": 40
}

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.10 each plus the $0.10 source check; billed deltas are capped at 500 per run.

🧾 JSON sample record

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

{
"record_key": "wipo:D2026-4000",
"case_number": "D2026-4000",
"complainant": "Associated Newspapers Limited DMG Media Limited",
"respondent": "-",
"domain_names": [
"elizafashion.com"
],
"decision": "Terminated",
"decision_url": null,
"decision_available": false,
"scope_note": "case index only; the index carries no dates and the decision text is not opened",
"record_type": "case_record",
"schema_version": "1.0",
"output_mode": "preview",
"preview_cap": 25,
"preview_truncated": 9
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

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 case delta is charged at the moment it is pushed (case-delta); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One source-check is charged per run that actually read the source.

First run and later runs — read this first

This Actor sells change detection, not bulk export. Two modes:

  • Snapshot (watch_mode: false, the prefilled default): returns current cases as a preview, hard-capped at 25 records regardless of max_items. Billed one source-check only — the preview records are not billed. Use it to see the data now.
  • Watch (watch_mode: true): the first run seeds a private baseline and emits zero deltas (billed one source-check). Every run after emits one delta per change — the value event. An outcome moving from Case active to a decision is exactly what you get a delta for. A blocked fetch is not diffed at all, so a source outage is never reported as a mass removal.

Source, scope and limits

WIPO gTLD decision index (wipo.int/amc/en/domains/decisionsx/), listing scope only — the case index, not the decision text. The WIPO index carries no dates: it reports that a case changed since your last run, not the day a decision issued (case numbers ascend with filing order, and that is the chronology the frontier walk follows). If you need decision dates they are in the decision text, which this Actor deliberately does not open. Snapshot mode is a capped preview. Terminal states: NORMAL · SUCCEEDED-0: GENUINE_EMPTY · SUCCEEDED-0 (no change) · PARTIAL · BLOCKED.

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.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different baseline_id for independent watches. 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
Source check (source-check)$0.10$0.09$0.08$0.07
Case Delta (case-delta)$0.10$0.09$0.08$0.07

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

  • 8 case deltas: $0.02 start + $0.10 source check + 8 × $0.10 = $0.92
  • 25 case deltas: $0.02 start + $0.10 source check + 25 × $0.10 = $2.62
  • 500 case deltas: $0.02 start + $0.10 source check + 500 × $0.10 = $50.12

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). 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 1024 MB.

Yield on the sample run: PARTIAL: emitted 25 item(s); PREVIEW: snapshot output is capped at 25 record(s); 9 further record(s) withheld. Use watch mode for the full change feed.. max_items is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

This actor reads public, logged-out pages and feeds published by www.wipo.int. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, 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 (www.wipo.int) 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 plus one source check.

Q: How many rows can one run return?
A: Up to max_items (default 500); snapshot previews stop at 25. 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 (baseline_id names it, so several independent watches can coexist). 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 www.wipo.int. 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 (max_items) 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.