Owner Analytics
Owners
Owner Analytics
Retrieve a composed analytics report for an owner
GET
Owner Analytics
When to use this
Use this endpoint to size a competitor’s trademark portfolio before filing an opposition or planning clearance work. It returns current portfolio totals and distributions in one request. Reports use a Valkey cache with a 24-hour TTL backstop and are invalidated by the nightly stats-computeowner.updated wave. Proceedings ingestion does not emit owner-grain events directly, so a newly ingested proceeding appears within about 24 hours. Server-Timing reports cache;desc="hit" or cache;desc="miss".
Path Parameters
Owner ID (
own_*).Example
Request
Response
Litigation fields
as_challenger covers disputes the owner brought as an opponent or petitioner. as_defendant covers disputes against marks the owner currently holds. win_rate is wins divided by decided, and is null when decided is zero. decided excludes settled, withdrawn, and pending proceedings. avg_duration_days is the mean number of days from filing to decision when both dates are available.
Transaction fields
by_type groups distinct recordings into conveyance-type buckets. acquired_count counts recordings where the owner is an assignee; divested_count counts those where it is an assignor. The first and last dates bound the recorded transaction history.
unreleased_security_interests counts security-interest recordings without a non-purged release pointing back to the same reel/frame, and marks_with_liens deduplicates marks attached to those recordings. Reel/frame linkage is authoritative: a security interest remains unreleased until a release recording points to it.
Acquirers use this block to gauge a brand’s transaction history, while lenders check for unreleased liens before extending credit. See list assignments, get an assignment, and the chain-of-title and lien diligence guide for recording-level detail.