> 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/collect.md).

# Collect: Employee API

Collect employee data using an employee ID, profile URL, or shorthand name.

{% columns %}
{% column width="16.666666666666664%" %}
Data type:

URLs:
{% endcolumn %}

{% column %}
Employee data

<https://api.coresignal.com/cdapi/v2/employee\\_multi\\_source/collect/{employee\\_id}\\>
<https://api.coresignal.com/cdapi/v2/employee\\_multi\\_source/collect/{profile\\_url/shorthand\\_name}>
{% endcolumn %}
{% endcolumns %}

***

## Overview

Find instructions for collection endpoint usage and data collection.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>General information about collection requests</td><td><a href="/api-introduction/requests/collect.md">Collect and Enrich</a></td></tr></tbody></table>

Use employee data collection endpoints to collect data using employee IDs, profile URLs or shorthand names.

| Used key       | Collect endpoints                                                                                                         | Function                                                                                                                                                                         |
| -------------- | ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Employee ID    | [*/v2/employee\_multi\_source/collect/{employee\_id}*](#collection-using-ids)                                             | Retrieved using Employee API search endpoints.                                                                                                                                   |
| Shorthand name | [*/v2/employee\_multi\_source/collect/{profile\_url/shorthand\_name}*](#collection-using-profile-urls-or-shorthand-names) | Use profile URL or shorthand name, taken directly from the URL (e.g., john-doe from *[www.professiona\\\_network.com/john-doe](http://www.professiona\\_network.com/john-doe)*). |

***

## Collection using IDs

Examples in this article are prepared using Postman. However, you can use the most convenient tool for you: terminal, Postman, or any API-compatible application.

### cURL (Postman)

Use the provided request template below. Enter a valid `employee_id` value and your `API Key`.

{% tabs %}
{% tab title="Full collect" %}
{% code title="cURL request template" %}

```json
curl -X 'GET' \
'https://api.coresignal.com/cdapi/v2/employee_multi_source/collect/{employee_id}' \
-H 'accept: application/json' \
-H 'apikey: {API Key}'
```

{% endcode %}
{% endtab %}

{% tab title="Field selection" %}
{% code title="cURL request template with several fields" %}

```json
curl -X 'GET' \
'https://api.coresignal.com/cdapi/v2/employee_multi_source/collect/{employee_id}?fields=full_name&fields=follower_count' \
-H 'accept: application/json' \
-H 'apikey: {API Key}'
```

{% endcode %}
{% endtab %}
{% endtabs %}

## Collection using profile URLs or shorthand names

Examples in this article are prepared using Postman. However, you can use the most convenient tool for you: terminal, Postman, or any API-compatible application.

### cURL (Postman)

Use the provided request template below. Enter a valid `profile_url` or `shorthand_name` value and your `API Key`.

{% tabs %}
{% tab title="Full collect" %}
{% code title="cURL request template" %}

```json
curl -X GET "https://api.coresignal.com/cdapi/v2/employee_multi_source/collect/{profile_url/shorthand_name}"
 -H  "accept: application/json" 
 -H  "apikey: {API Key}"
```

{% endcode %}
{% endtab %}

{% tab title="Field selection" %}
{% code title="cURL request example with several fields" %}

```json
curl -X GET "https://api.coresignal.com/cdapi/v2/employee_multi_source/collect/{profile_url/shorthand_name}?fields=full_name&fields=follower_count"
 -H  "accept: application/json" 
 -H  "apikey: {API Key}"
```

{% endcode %}
{% endtab %}
{% endtabs %}

***

## Bundles collect

By default, a collect request returns the full employee data. Use the `bundle` query parameter to get only the requested bundle. The `bundle` parameter can be repeated to request several bundles. Accepted values:

{% hint style="info" %}
The `bundle` parameter is optional, and omitting it returns the full record.
{% endhint %}

<table><thead><tr><th width="269.6796875">Requested bundle</th><th width="330.45703125">Bundle value - query parameter name</th><th>Credit amount</th></tr></thead><tbody><tr><td><a href="/employee-data/bundles/core.md">Core Employee data</a></td><td><code>core_employee_data</code></td><td>10</td></tr><tr><td><a href="/employee-data/bundles/employer-information.md">Employer information</a></td><td><code>employer_information</code></td><td>4</td></tr><tr><td><a href="/employee-data/bundles/career-intelligence.md">Career intelligence</a></td><td><code>career_intelligence</code></td><td>3</td></tr><tr><td><a href="/employee-data/bundles/social-influence.md">Social influence</a></td><td><code>social_influence</code></td><td>3</td></tr></tbody></table>

{% code title="cURL request example with bundles" %}

```json
curl -X 'GET' \
'https://api.coresignal.com/cdapi/v2/employee_multi_source/collect/{employee_id}?bundle=core_employee_data&bundle=social_influence' \
 -H  "accept: application/json" 
 -H  "apikey: {API Key}"
```

{% endcode %}

The `fields` parameter narrows the results within the selection. If a field is outside the selected bundles, the request returns a `400` error identifying the bundle that owns the field.

***


---

# 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/collect.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.