> 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/additional-sources/professional-network-data.md).

# Professional Network Data

Fresh Professional network data can be used by multiple industries, including sales tech, market research, investment, risk assessment, and HR.

Fresh, publicly available professional network data, structured into company, employee, and job records that you can query via the API or download as flat files.

## Ready to use

We continuously collect professional network data and organize it into company, employee, and job records as it arrives, so you’re working with current conditions, not a snapshot from months ago.

| **Ready to use right away** | Data is organized into clear fields as it’s collected, so you can start querying or loading it without extra processing.                |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Timestamped records**     | Each record includes a timestamp from its latest collection cycle, so you can check how current it is before using it.                  |
| **Worldwide coverage**      | Records span companies, professionals, and job postings across the globe, all drawn from one continuously updated professional network. |

{% hint style="success" %}

#### Need unprocessed professional network data? Access on demand

[Contact our sales](https://coresignal.com/contact-us/) team to discuss dataset and API access, pricing, and fields beyond what is shown here.
{% endhint %}

## Three datasets built from one professional network

Each dataset is collected on an ongoing basis and delivered as flat files or through its own API, with fields for the signals most relevant to your needs.

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><h4>Company Data</h4></td><td>Core firmographic, organizational, and geographic data, collected continuously since 2016. Categorize companies by size, industry, and age, map their locations, and monitor structural changes, such as headcount, over time.</td></tr><tr><td><h4>Employee Data</h4></td><td>Professional profile data, collected continuously since 2016, supports HR technology, talent intelligence, and large-scale lead enrichment. Profiles are rechecked on a rolling basis, with priority given to the most recent changes.</td></tr><tr><td><h4>Jobs Data</h4></td><td>Global job postings tracked continuously since August 2020, with 24/7 discovery and daily status rechecks, so you can see what companies are hiring for as it happens.</td></tr></tbody></table>


---

# 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/additional-sources/professional-network-data.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.
