TMview global trademark search API: access card

Every endpoint on this page was live-probed on 2026-07-29 by the Aidenix Atlas catalog.

What is the TMview multi-register search?

TMview global trademark search API is the EU Intellectual Property Office's cross-register search — one query covers USPTO, EUIPO, WIPO and dozens of national trademark offices, published by EUIPO — TMDN network. Coverage: Global; scale: national and international registers combined — 5,122 records match ACME across all offices. In our data — the Aidenix Atlas catalog, where every source is live-probed — this endpoint answered HTTP 200 on 2026-07-29. What the card gives you:

• The exact endpoint and a working request you can copy.
• Authentication and rate limits: none — no API key required.
• The query keys the source accepts and the fields it returns, verified against the live endpoint.

Key facts at a glance

A key-facts table is the 30-second version of this card: national and international registers combined — 5,122 records match ACME across all offices in scope, 3 query facets, 8 field groups out. Every row comes from our own probe run of 2026-07-29, not from vendor marketing:

How do you query it?

A working query is one plain HTTP request — in our data this exact request form was verified on 2026-07-29:

curl -X POST "https://www.tmdn.org/tmview/api/search/results" \
  -H "Content-Type: application/json" \
  -d '{"page":"1","pageSize":"30","criteria":"C","basicSearch":"acme"}'

Client quirks we hit while probing this source:

• The server drops connections from non-browser User-Agent strings — a plain script client reads as a dead endpoint until you set one.
• Page size is fixed at 30 records per call; paging is via page.
• Applicant names arrive in the script of the filing office, so the same company appears under several alphabets — match on mark plus office, never on the name string alone.

When should you use this source?

A source fit is a match between what you already know and what the endpoint accepts — 3 query facets here, according to our probe of 2026-07-29. In our data, the decision goes like this:

• If the company is registered in Global → this is the authoritative record, filed with EUIPO — TMDN network.
• If you can search by trademark name → this source resolves it directly; other facets need a different registry.
• If you need fields it does not return (trademark name, IP office, applicant name, Nice class, status, application number, registration number, dates is the full list) → follow the related sources below rather than forcing this one.

What does it accept and return?

The interface contract is a short one: 3 query facets in, 8 field groups out. Every row below was checked against the live endpoint on 2026-07-29:

Related sources

A related source is a dataset that joins to the TMview multi-register search through a shared key — 2 of them in our catalog of nearly 4,000 sources, each probed on the same schedule as this card, according to our run of 2026-07-29:

• USPTO trademark full-text search API — United States (federal).
• UK Companies House API — United Kingdom.
• New York business entity search — resolve a US owner name to its registry record.
• Company data API guide — the full set of open routes an owner name can land in.

The workflow this source belongs to is covered in the full guide: Free trademark search API — USPTO and global registers.

Frequently asked questions

Three questions cover most of what people ask about this source. Answers below reflect our probe of 2026-07-29:

Is the TMview multi-register search free to use? Yes — $0 license fee, national and international registers combined — 5,122 records match ACME across all offices in scope, authentication: none — no API key required. The cost of using it is engineering time and rate-limit patience, not money.

How current is the data? The records are as current as EUIPO — TMDN network makes them — registries update on filing schedules, not news cycles. What we verify is the endpoint: it answered on 2026-07-29, and this card carries that date so you can tell a fresh claim from a stale one.

Can I use this commercially? Public records generally allow commercial use, but terms are set per publisher, not universally. Query-and-enrich workloads are uncontroversial; verify EUIPO — TMDN network's specific terms before redistributing bulk copies.

How we verify this card

Our verification method is a live probe, not a citation chain — the status on this card comes from a real request we sent on 2026-07-29. What the probe run covers, in our data:

• Endpoint liveness: this source is one of the nearly 4,000 the Aidenix Atlas catalog tracks, re-probed on schedule.
• Contract checks: the accepted query facets and returned field groups above are read from the live response, not from documentation.
• Honest failures: when a source stops answering, this card says so and its date freezes — we do not publish a fresh-looking date over a dead endpoint.
• Freshness contract: the «last probe» date above is the promise; it moves only when the source actually answers.

Source card generated from the Aidenix Atlas catalog; facts as probed on 2026-07-29.