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

# Output Response - Company Enrichment API

## Response Data Structure

Here is an example response from the Company Enrichment API:

```json
{
  "status": 200,
  "name": "people data labs",
  "id": "tnHcNHbCv8MKeLh92946LAkX6PKg",
  ...,
  "likelihood": 6
}
```

See [Example Company Record](https://docs.peopledatalabs.com/docs/example-company-record) for a full example of the fields included in the response object.

## Response Fields

### `*`

| Type  | Description                                                                                      |
| :---- | :----------------------------------------------------------------------------------------------- |
| `any` | The matched company profile in the format described in our [Company Schema](https://docs.peopledatalabs.com/docs/company-schema). |

The [PDL profile](https://docs.peopledatalabs.com/docs/company-schema) for the company that matches the Enrichment API request. Any profile field that we do not have data for will have a `null` value.

Unlike our other APIs, the profile fields for the Company Enrichment API are **NOT** contained in a top-level `data` object.

<br />

### `status`

| Type      | Description                          |
| :-------- | :----------------------------------- |
| `Integer` | The [API response code](https://docs.peopledatalabs.com/docs/errors). |

<br />

### `likelihood `

<Table align={["left","left"]}>
  <thead>
    <tr>
      <th>
        Type
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `Integer`
      </td>

      <td>
        How confident we are that the returned profile is the same as the company you requested. Will be an integer between `1` and `10`.

        You can control the minimum likelihood score that a response must have in order to count as a match by setting the [`min_likelihood` parameter](https://docs.peopledatalabs.com/docs/input-parameters-company-enrichment-api#min_likelihood) in the API request.
      </td>
    </tr>
  </tbody>
</Table>

We assign every match that the API finds during the enrichment process a likelihood score, to represent our confidence that the profile returned is the same as the profile requested. A score of `1` represents a very low confidence level while a score of `10` represents the highest degree of confidence. The likelihood score is logarithmic, so a response that returns a likelihood score of `2` will have roughly a 10-30% chance of being the person requested.

For example, enriching "John Smith, Inc." in "New York" is too vague for us to confidently say which of our profiles is the exact John Smith Inc. that you requested. However, if you were to attach a website, stock ticker, and street address to the request and they matched our data, we would be highly confident that we are returning the correct John Smith Inc.

<br />

### `matched`

<Table align={["left","left"]}>
  <thead>
    <tr>
      <th>
        Type
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `Array (String)`
      </td>

      <td>
        Every query input from the request that matched this profile.

        * \*IMPORTANT:\*\* This field will only be included in the response if the [`include_if_matched` flag](https://docs.peopledatalabs.com/docs/input-parameters-company-enrichment-api#include_if_matched) is set to `true`.
      </td>
    </tr>
  </tbody>
</Table>

See the [`include_if_matched` input parameter](https://docs.peopledatalabs.com/docs/input-parameters-company-enrichment-api#include_if_matched) for more details.