> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/employee-data/api/contact-enrichment-api.md).

# Contact Enrichment API

Enrich employee records with business email addresses using Clean Employee IDs.

Enrich collected employee data with publicly available business contact information\
using the Contact Enrichment API and employee IDs. Combined with our regularly\
refreshed employee data, the API provides up-to-date business contacts.

#### Contact Enrichment API endpoint

| Endpoint                                                                                     | Input       | Output                 |
| -------------------------------------------------------------------------------------------- | ----------- | ---------------------- |
| <p>GET<br><code><https://api.coresignal.c></code><br><code>om/enrichment/contacts</code></p> | Employee ID | Business email address |

#### Enrich contact data

Use employee IDs to enrich the data. Query Parameters: `member_id={employee ID}`.

{% code title="" expandable="true" %}

```json
curl --location --request GET
"https://api.coresignal.com/enrichment/contacts?member_id=123"
-H "apikey: {API Key}"
```

{% endcode %}

#### Sample response

{% code title="" expandable="true" %}

```json
{
"code":0,
"message":"FOUND",
"data":{
"email_status":"catch_all",
"email":"john.doe@company.com",
"email_confidence": 100
}
```

{% endcode %}

#### Data dictionary

<table><thead><tr><th width="184.63671875">Data field</th><th width="252.13671875">Description</th><th width="146.12890625">Data type</th><th>Possible values</th></tr></thead><tbody><tr><td><code>code</code></td><td>Returned response<br>code</td><td>Integer</td><td><code>0</code>,<code>1</code>,<code>2</code></td></tr><tr><td><code>message</code></td><td>Indication if contact<br>was found</td><td>String</td><td><code>FOUND</code>,<br><code>NOT_FOUND</code></td></tr><tr><td><code>data</code></td><td>Data values if it was<br>found</td><td>Struct</td><td><code>null</code> or fields<br>below</td></tr><tr><td><code>data.email_status</code></td><td>Listed email status</td><td>String</td><td><code>verified</code>,<br><code>catch_all</code></td></tr><tr><td><code>data.email</code></td><td>Email address<br>connected to the<br>submitted<br>employee ID</td><td>String</td><td><code>john.doe@examplec</code><br><code>ompany.com</code></td></tr><tr><td><code>data.email_confid</code><br><code>ence</code></td><td>Confidence score<br>assigned to the<br>email address</td><td>Integer</td><td><code>100</code></td></tr></tbody></table>

#### Available response codes

<table><thead><tr><th width="288.02734375">Response code</th><th width="373.64453125">Description</th></tr></thead><tbody><tr><td><code>0</code></td><td>Request is successful, data returned</td></tr><tr><td><code>1</code></td><td><code>member_id</code> is not available in our database<br><img src="https://458921062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcyJAXlZjTKSLvAQjb9rM%2Fuploads%2FGjNTHg6jsJIdMH1VrfoX%2Fcode_block_cropped.png?alt=media&amp;token=91d2dd11-47eb-41ff-8329-e360800a780b" alt=""></td></tr><tr><td><code>2</code></td><td>Information is not accessible due to privacy<br>regulations (EEA and UK employees)</td></tr></tbody></table>

#### Limitations

Due to privacy regulations, records identified as relating to individuals in the\
European Economic Area (EEA) or the United Kingdom (UK) are excluded from this\
enrichment endpoint. In these cases, you will see the following response:

{% code title="Data is not accessible" expandable="true" %}

```json
{
"code": 2,
"message": "NOT_ACCESSIBLE",
"data": null
}
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/employee-data/api/contact-enrichment-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.