/api/v1/patents/:patentIdPatent Full Record
Retrieve ONE patent's full record by its publication identifier (e.g. WO2021098789A1, EP3823456A1): abstract, inventors, classifications with CPC descriptions, family members, legal/priority/application dates, patent + NPL citations, graph-enriched citation counts, and resolved_assignees whose rows carry the full resolution chain (mention_id / direct_id / ultimate_id, with organization_id kept as the mention_id alias). Any of those ids is directly reusable as the company_id filter on patents.search / patents.aggregate / patents.yoy-growth - this closes the assignee -> portfolio chain. Responses use implicit 2xx (no success flag). Requires a Pro workspace (returns HTTP 402 otherwise).
When to use it
- full record for one patent by publication id
- citations, family members and legal status for a patent
- resolve a patent's assignee to an organization id for portfolio queries
Getting started
Base URL
https://app.caelrith.com/api/v1/toolsAuthentication
Include your API key in the x-api-key header.
Parameters
Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| patentId(path) | string | Yes | Patent publication identifier, e.g. WO2021098789A1 or EP3823456A1. Copy it from a patents.search result's patent_id; never construct or guess it. |
Query parameters
No parameters.
Example request
curl -H "x-api-key: YOUR_API_KEY" \
"https://app.caelrith.com/api/v1/patents/{patentId}"Response envelope
This endpoint returns an implicit 2xx response - there is no success flag in the body.
{
"data": { /* payload */ },
"meta": { /* pagination, totals */ }
}
// No "success" flag on this endpoint - any 2xx JSON is a success.Response shape
Payload: data.resolved_assignees — Resolved Assignees (secondary list)
Common row fields
| Field | Description |
|---|---|
| patent_id | Record identifier |
| title | Main display field |
| mention_id | — |
| direct_id | — |
| ultimate_id | — |
| raw_name | — |
Empty results: No record found (HTTP 404)
resolved_assignees rows carry the full resolution chain: mention_id (raw mention node), direct_id (first resolved entity), ultimate_id (top of the parent_of climb = the id stored in the patent's assignees_resolved_ids), plus organization_id (alias of mention_id). ANY of these ids is directly reusable as the company_id filter on patents.search / patents.aggregate / patents.yoy-growth - pass it verbatim (assignee -> portfolio chain). 'assignees' holds raw names; resolved_assignees may be empty when resolution failed - in that case pass the raw assignee string as company_id (it resolves via the mention key).
Catalog version 0.0.0-generated · generated from the API source