> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enrow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Bulk Email Results

> Retrieve the results, stats, and credit breakdown of a bulk email search by batch ID

<Badge color="blue">GET</Badge>

```
https://api.enrow.io/email/find/bulk?id={id}
```

Retrieve all results from a batch email search using the batch ID. Authenticate every request with your [API key](/authentication) in the `x-api-key` header. The batch ID is the `id` returned when you start a job with the [Find Bulk Emails](/api-reference/email-finder/find-bulk) endpoint.

<Info>
  Using a webhook allows you to skip calling this GET endpoint. See [How Webhooks Work](/how-webhooks-work).
</Info>

## Query Parameters

<ParamField query="id" type="string" required>
  The `id` returned from the POST request
</ParamField>

## Response

### 200 — Search completed

<ResponseField name="general" type="object">
  Batch metadata

  <Expandable title="general properties">
    <ResponseField name="id" type="string">
      Batch identifier
    </ResponseField>

    <ResponseField name="status" type="string">
      `completed`, `ongoing`, or `failed`
    </ResponseField>

    <ResponseField name="custom" type="object">
      Custom properties passed in the original request, returned as-is
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="stats" type="object">
  Batch statistics

  <Expandable title="stats properties">
    <ResponseField name="finished" type="number">
      Number of searches completed
    </ResponseField>

    <ResponseField name="requested" type="number">
      Total number of searches requested
    </ResponseField>

    <ResponseField name="valid" type="number">
      Number of valid emails found
    </ResponseField>

    <ResponseField name="credits_cost" type="object">
      Credit breakdown. Credits are refunded for invalid or not-found results — see [Credits & billing](/credits-billing) for how charges and refunds work.

      <Expandable title="credits_cost properties">
        <ResponseField name="initial" type="number">
          Credits initially charged
        </ResponseField>

        <ResponseField name="refunded" type="number">
          Credits refunded (for invalid/not found)
        </ResponseField>

        <ResponseField name="final" type="number">
          Final credit cost
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="results" type="array">
  Array of search results

  <Expandable title="Result properties">
    <ResponseField name="index" type="string">
      Position in the original search array
    </ResponseField>

    <ResponseField name="qualification" type="string">
      `valid` (email found) or `invalid` (email not found). [Why binary?](/status-codes#why-binary)
    </ResponseField>

    <ResponseField name="email" type="string">
      The discovered email address (when `valid`)
    </ResponseField>

    <ResponseField name="info" type="object">
      Contact info: `domain`, `firstname`, `lastname`, `gender`, `companyInfo`. The `firstname` and `lastname` values are capitalized. `info` is only present for valid results.
    </ResponseField>

    <ResponseField name="raw_params" type="object">
      The original search parameters sent
    </ResponseField>

    <ResponseField name="custom" type="string | object">
      Custom data passed in the original search
    </ResponseField>
  </Expandable>
</ResponseField>

### 200 — Search still in progress

While the batch is running, the GET endpoint returns HTTP `200` with a reduced body of the shape `{ general: { id, status: "ongoing" }, stats: { finished, requested } }`.

<ResponseField name="general" type="object">
  `id` and `status: "ongoing"`
</ResponseField>

<ResponseField name="stats" type="object">
  `finished` and `requested` counts
</ResponseField>

### Error Responses

| Code    | Message                                  |
| ------- | ---------------------------------------- |
| **400** | `Could not retrieve bulk search results` |

See [Error handling](/error-handling) for the full list of status codes and response formats.

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://api.enrow.io/email/find/bulk?id=3d4cb64e-i64d-41e8-a686-736751004a32' \
    --header 'x-api-key: YOUR_API_KEY'
  ```

  ```javascript Node.js theme={null}
  const batchId = '3d4cb64e-i64d-41e8-a686-736751004a32';
  const response = await fetch(`https://api.enrow.io/email/find/bulk?id=${batchId}`, {
    headers: {
      'x-api-key': process.env.ENROW_API_KEY
    }
  });

  const data = await response.json();
  if (data.general.status === 'completed') {
    console.log(`Valid: ${data.stats.valid}/${data.stats.requested}`);
    console.log(data.results);
  }
  ```

  ```python Python theme={null}
  import requests
  import os

  batch_id = "3d4cb64e-i64d-41e8-a686-736751004a32"
  url = f"https://api.enrow.io/email/find/bulk?id={batch_id}"
  headers = {
      "x-api-key": os.getenv("ENROW_API_KEY")
  }

  response = requests.get(url, headers=headers)
  data = response.json()
  if data["general"]["status"] == "completed":
      print(f"Valid: {data['stats']['valid']}/{data['stats']['requested']}")
  ```
</RequestExample>

<ResponseExample>
  ```json Success Response theme={null}
  {
    "general": {
      "id": "3d4cb64e-i64d-41e8-a686-736751004a32",
      "status": "completed",
      "custom": "campaign_q2"
    },
    "stats": {
      "finished": 3,
      "requested": 3,
      "valid": 2,
      "credits_cost": {
        "initial": 3,
        "refunded": 1,
        "final": 2
      }
    },
    "results": [
      {
        "index": "0",
        "qualification": "valid",
        "email": "dwight.schrute@dundermifflin.com",
        "info": {
          "domain": "dundermifflin.com",
          "firstname": "Dwight",
          "lastname": "Schrute",
          "companyInfo": {
            "name": "Dunder Mifflin"
          }
        },
        "raw_params": {
          "company_domain": "dundermifflin.com",
          "fullname": "Dwight Schrute"
        },
        "custom": "lead_001"
      },
      {
        "index": "1",
        "qualification": "valid",
        "email": "jim.halpert@dundermifflin.com",
        "info": {
          "domain": "dundermifflin.com",
          "firstname": "Jim",
          "lastname": "Halpert",
          "companyInfo": {
            "name": "Dunder Mifflin"
          }
        },
        "raw_params": {
          "company_domain": "dundermifflin.com",
          "fullname": "Jim Halpert"
        },
        "custom": "lead_002"
      },
      {
        "index": "2",
        "qualification": "invalid",
        "email": null,
        "raw_params": {
          "company_domain": "dundermifflin.com",
          "fullname": "Ryan Howard"
        },
        "custom": "lead_003"
      }
    ]
  }
  ```

  ```json Error Response theme={null}
  {
    "message": "..."
  }
  ```
</ResponseExample>

## Next steps

<CardGroup cols={2}>
  <Card title="Find emails in bulk" icon="layer-group" href="/api-reference/email-finder/find-bulk">
    Start a new batch of up to 5,000 email searches.
  </Card>

  <Card title="Webhooks" icon="bell" href="/how-webhooks-work">
    Skip polling and get notified when a batch completes.
  </Card>

  <Card title="Credits & billing" icon="coins" href="/credits-billing">
    See how credits are charged and refunded per result.
  </Card>

  <Card title="Verify emails in bulk" icon="circle-check" href="/api-reference/email-verifier/verify-bulk">
    Validate a list of email addresses in a single batch.
  </Card>
</CardGroup>