> 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/company-data/api/enrich.md).

# Enrich: Company API

Enrich company data from a website URL with the Company API.

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

URL:
{% endcolumn %}

{% column %}
Company data

<https://api.coresignal.com/cdapi/v2/company\\_multi\\_source/enrich?website={URL}>
{% endcolumn %}
{% endcolumns %}

***

## Overview

Find instructions for using the collection endpoint and collecting data.

<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 collect requests</td><td><a href="/api-introduction/requests/collect.md">Collect and Enrich</a></td></tr></tbody></table>

Use the company enrichment endpoint to collect company data using websites or social media profile URLs as input.

| Used key    | Collect endpoint                                  | Function                               |
| ----------- | ------------------------------------------------- | -------------------------------------- |
| Website URL | */v2/company\_multi\_source/enrich?website={URL}* | Obtain company data using website URLs |

***

## Collection using websites

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)

Paste the website URL instead of `{URL}` and API Key instead of `{API Key}` in the request template:

{% code title="Template" %}

```json
curl -X 'GET' \
  'https://api.coresignal.com/cdapi/v2/company_multi_source/enrich?website={URL}' \
  -H 'accept: application/json' \
  -H 'apikey: {API Key}'
```

{% endcode %}

Here is an example of full collect and selected fields collection:

{% tabs %}
{% tab title="Full collect" %}
{% code title="Request example" %}

```json
curl -X 'GET' \
  'https://api.coresignal.com/cdapi/v2/company_multi_source/enrich?website=thermofisher.com' \
  -H 'accept: application/json' \
  -H 'apikey: {API Key}'
```

{% endcode %}
{% endtab %}

{% tab title="Fields selection" %}
{% code title="Request example" %}

```json
curl -X 'GET' \
  'https://api.coresignal.com/cdapi/v2/company_multi_source/enrich?website=thermofisher.com&fields=id&fields=company_name' \
  -H 'accept: application/json' \
  -H 'apikey: {API Key}'
```

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

***

## Bundles enrich

By default, an enrich request returns the full company data record. To request only part of it, use the bundle query parameter. You can repeat bundle once for each bundle to combine several.

| Requested bundle                                                          | Bundle value - query parameter name |
| ------------------------------------------------------------------------- | ----------------------------------- |
| [Core company data](/company-data/bundles/core.md)                        | `core_company_data`                 |
| [Financial information](/company-data/bundles/financial-information.md)   | `financial_information`             |
| [Growth signals](/company-data/bundles/company-growth-signals.md)         | `growth_signals`                    |
| [Workforce intelligence](/company-data/bundles/workforce-intelligence.md) | `workforce_intelligence`            |
| [Company intelligence](/company-data/bundles/company-intelligence.md)     | `company_intelligence`              |

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

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

```json
curl -X 'GET' \
  'https://api.coresignal.com/cdapi/v2/company_multi_source/enrich?website={URL}&bundle=core_company_data&bundle=financial_information' \
  -H 'accept: application/json' \
  -H 'apikey: {API Key}'
```

{% endcode %}

The `fields` parameter narrows the results within the selection. If a field isn’t part of the selected bundles, the request returns a `400` error identifying the bundle that owns it.

***


---

# 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/company-data/api/enrich.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.