Get resolve parent result
Returns the status and result of a parent hierarchy resolution job. When status is completed, the record object contains the parent hierarchy data.
Status lifecycle
Jobs progress linearly to a terminal state:completed or failed, the status does not change.
Result structure
Whenstatus is completed, the record field contains the parent hierarchy data with parent, top_parent, top_operating_parent (conditionally present), and regional_subsidiary.
For pending or processing jobs, only status is returned. For failed jobs, record is absent and error_message with error_type are present instead.
Example
Response fields
record.parent
object | null — The immediate parent entity. null when the entity has no parent (standalone).
record.top_parent
object | null — The ultimate parent entity at the top of the corporate hierarchy. For standalone entities, top_parent points to the entity itself and parent is null. Has the same fields as parent except it does not include reasoning (only confidence).
record.top_operating_parent
object | null — The topmost operating company (excluding HoldCo/investment vehicles) found by looking up the corporate hierarchy from the queried entity.
This field is conditionally present:
- Present when the entity is an operating company or when an operating company is found above it in the hierarchy
- Omitted for standalone entities that are not operating companies (e.g. HoldCos with no tree)
null if no operating company exists in the upward chain (e.g. a HoldCo whose entire parent chain consists of other HoldCos).
Has the same fields as top_parent (no reasoning, includes confidence).
record.regional_subsidiary
object — Whether the queried entity operates as a regional subsidiary of its parent.
Polling guidance
- Use exponential backoff between polls (start at 2 seconds, cap at 30 seconds).
- Jobs that do not exist yet (or whose ID is unknown) return
{ "status": "pending" }.
Related endpoints
- Resolve parent — Start a parent hierarchy resolution job
Authorizations
Include your API key in the x-api-key header.
Path Parameters
Job ID returned by the POST endpoint
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"
Response
Job status response
Current status of the job. Terminal states are completed and failed.
pending, processing, completed, failed Unique identifier for the job. Present when status is pending, processing, or completed.
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"
Unique identifier for the job. Present only when status is failed.
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"
ISO 8601 timestamp when the job was created.
"2025-06-05T12:00:00Z"
ISO 8601 timestamp when the job reached a terminal state.
"2025-06-05T12:00:05Z"
Parent hierarchy data. Present when status is completed.
Error message. Present when status is failed.
Machine-readable error type. Present when status is failed. One of: kernel_id_not_found, unknown.

