Skip to main content
GET
Entity Analytics

When to use this

Audit a conglomerate’s global trademark footprint across all its resolved subsidiaries in one call. The report deduplicates marks shared by multiple member owners and groups Madrid designations under their International Registration. Reports use a Valkey cache with a 24-hour TTL backstop and are invalidated by the nightly stats-compute entity.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

string
required
Entity ID (ent_*).

Code Examples

Litigation fields

as_challenger covers disputes the entity’s member owners brought as opponents or petitioners. as_defendant covers disputes against marks those owners currently hold. 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 family recordings into conveyance-type buckets. acquired_count counts recordings with a family owner as assignee; divested_count counts those with one as assignor. The first and last dates bound the recorded family 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 family’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.

Large entities

Entities resolve to at most 10,000 live member owners. Larger portfolios return 422 entity_too_large with error.reason set to member_owners_too_large, plus member_count and member_count_limit. If resolution exceeds the bounded corporate family graph walk instead, the same 422 entity_too_large response uses error.reason: family_graph_too_large, plus related_entity_limit and depth_limit.