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

# Company Data Flat Files

Get Company Data in JSONL or Parquet files with daily, monthly, or quarterly delivery options for analytics and warehouse pipelines.

Flat files are one of two methods Coresignal uses to deliver Company Data. Instead of manually querying records, you receive the dataset or periodic updates as a downloadable file that you can load directly into your warehouse or pipeline. This page explains how flat file delivery works for Company Data, including the available formats and delivery frequency.

## Delivery frequency and formats

Company Data is available in:

* **Parquet** for efficient storage and analytics workloads.
* **JSONL** for streaming and line-by-line processing.

Files are delivered daily, monthly and quarterly. Historical fields let you measure changes in company metrics over time.

| Dataset      | Delivery frequency        | Delivery format | Update frequency |
| ------------ | ------------------------- | --------------- | ---------------- |
| Company Data | Daily, monthly, quarterly | JSONL, Parquet  | Ongoing          |

{% hint style="info" %}
Use a stable company identifier when joining files across deliveries. This helps preserve company history when names or URLs change.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Explore full company record sample</td><td><a href="/company-data/record-sample.md">Company Record Sample</a></td></tr><tr><td>More information about flat files deliveries</td><td><a href="/introduction/delivery-formats.md">Delivery Formats</a></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/company-data/dataset.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.