> 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/social-posts-data/company-posts.md).

# Company Posts Data

The most recent and historical company posts and communications data from public companies for tracking launches, hiring signals, partnerships, and other updates.

Company Posts data is designed to be used in **Sales Tech, Investment, Market Research, and AI/ML applications.**

| **Company intelligence**                    | Captures companies' public communications, like product launches, hiring signals, and partnerships, without news aggregator filtering. Ideal for ABM tools and sales teams that need to act on business development moments as they happen. |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Embedded within the company's ecosystem** | Posts are natively joined to existing company datasets via `company_source_id` or `company_id` – no separate identity resolution step is required.                                                                                          |
| **Historical depth**                        | With historical data reaching back to 2016, the archive offers robust longitudinal context, enabling trend analysis, baseline benchmarking, and long-cycle account monitoring.                                                              |

***

### Summary

| Feature            | Details           |
| ------------------ | ----------------- |
| Available via      | Flat files/API    |
| Delivery frequency | Daily and monthly |
| Available formats  | JSONL, Parquet    |
| Scraping since     | 2026-05           |

#### Related links

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><a href="/social-posts-data/company-posts/data-dictionary.md">Dictionary: Company Posts Data</a></td></tr><tr><td><a href="/social-posts-data/company-posts/record-sample.md">Sample: Company Posts Data</a></td></tr><tr><td><a href="/social-posts-data/company-posts-api.md">Company Posts API</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/social-posts-data/company-posts.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.