# Bulk work email lookup status and results

Return a bulk work email lookup batch. Poll until `status` is `completed`, at which point `results` holds one result per submitted lookup, in the order they were submitted, each with the same shape as a single lookup result. `results` is empty until then, so a partial answer is never mistaken for a whole one.

Endpoint: GET /api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/bulk/{batch_id}/
Version: 1.0.0
Security: Api-Key

## Security:

  - `Api-Key` (unknown)
    apiKey in header X-API-KEY

## Path parameters:

  - `account_id` (integer, required)

  - `batch_id` (string, required)

## Response 200 fields (application/json):

  - `batch_id` (string, required)

  - `status` (string, required)
    * `queued`
 - Queued
* `running`
 - Running
* `completed`
 - Completed
* `failed`
 - Failed
    Enum: "queued", "running", "completed", "failed"

  - `item_count` (integer, required)
    How many rows this batch holds.

  - `date_created` (string, required)

  - `date_completed` (string, required)

  - `results` (array, required)

  - `results.submitted_index` (integer, required)
    Zero-based position of this row in the `email_lookups` array you submitted, so results can be matched back to your input order.

  - `results.job_id` (string, required)

  - `results.status` (string, required)
    * `queued`
 - Queued
* `running`
 - Running
* `awaiting_provider`
 - Awaiting provider
* `completed`
 - Completed
* `failed`
 - Failed
    Enum: "queued", "running", "awaiting_provider", "completed", "failed"

  - `results.emails` (array, required)
    Every confirmed address for this person, shortest first, each with its verdict.

  - `results.error_code` (any, required)

  - `results.person_id` (integer, required)

  - `results.submitted_lookup` (object, required)
    Echo the row exactly as it was sent.
Nested rather than four top-level fields, so "what you sent" is never
confused with "what we searched", and so the top level keeps its rule
that an absent value is `null` - here a blank string is the honest echo.
Spelled out key by key rather than dumped from the stored model, so a
new column on `SubmittedFields` becomes a deliberate addition here
instead of appearing in the response unasked.

  - `results.submitted_lookup.first_name` (string, required)

  - `results.submitted_lookup.last_name` (string, required)

  - `results.submitted_lookup.domain` (string, required)

  - `results.submitted_lookup.linkedin_public_identifier` (string, required)

  - `results.date_created` (string, required)

  - `results.date_completed` (string, required)

  - `results.result` (string, required)

