Get a Lookup Job's State and the Records Its Article Names
Returns the job state: 202 with Retry-After while PENDING or RUNNING, 200 once terminal. Once COMPLETED, it returns each identified name: MATCHED names the stored record, NEEDS_REVIEW lists candidates, and a failed name carries failureReason. Ordinary article jobs may include shell, enrichmentRunId, or shellDetail on NO_MATCH. Bulk jobs return maxNames and limitReached; reaching the bound means more names may remain. A single-subject job, filed by Prefer: respond-async on POST /v1/lookup with kind in the JSON body, or by a signed-in live lookup on that route that rolled over to a job, carries source.subject and, once COMPLETED, identification: the answer that route returns. Only the requesting caller can read the job.
Authentication
Your aVenture API key (https://aventure.vc/settings/api-keys) or OAuth access token
Path parameters
Response headers
Revision of this job snapshot; send it as If-None-Match for 304
Requests allowed per client IP in the current rate-limit window.
Requests left before the tightest applicable rate-limit bucket rejects.
Seconds until the exhausted rate-limit bucket admits another request; 0 when none is exhausted.
Response
The job is terminal: COMPLETED, FAILED, or CANCELED.
True when a bulk lookup returned its name bound; more names may remain. False does not prove that extraction found every name on a page.
Each identified company and person; bulk results are available while running.
Names processed so far, including per-name failures.
Whether retrying the failed lookup can succeed: TERMINAL when the job judged the failure not transient, TRANSIENT when a transient failure exhausted or lacked its retry budget; absent unless state is FAILED and the job recorded that decision.
Why the job failed; absent unless state is FAILED.
Subject jobs only: once COMPLETED, the identification returned for source.subject by POST /v1/lookup (kind in the JSON body), including requested filing and source-claim outcomes; absent otherwise.
Most names a bulk lookup accepts; absent for older article jobs.
Distinct names found for a bulk lookup; absent on standard jobs.
Stored article behind a shared-article lookup, when known.