Get entity resolution result
Returns the status and result of an entity resolution job. When status is completed, the record object contains the resolved entity data.
id returned by Resolve entity to check the status and retrieve the result.
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 resolved identity with confidence levels and structured legal and trading information. If you included an external_id in the original request, it is echoed back on record.external_id so you can correlate the result with the record you submitted.
For pending or processing jobs, record is absent. For failed jobs, record is absent and error_message with error_type are present instead.
Example
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" }.
Polling example
IdentityResult schema, see Completed result.Authorizations
Include your API key in the x-api-key header.
Path Parameters
Job ID returned by the POST endpoint
"550e8400-e29b-41d4-a716-446655440000"
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.
"550e8400-e29b-41d4-a716-446655440000"
Unique identifier for the job. Present only when status is failed.
"550e8400-e29b-41d4-a716-446655440000"
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"
Result payload. 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.

