> 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/employee-posts-api.md).

# Employee Posts API

Employee Posts API overview: search and collect fresh employee-published posts via Search Filters or Elasticsearch DSL, with Collect endpoint support.

## Overview

This section covers basic information on the Employee Posts API.

To learn more about the API and its endpoints, follow the links below:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Employee Posts API endpoints</td><td><a href="/social-posts-data/employee-posts-api.md#employee-posts-api-endpoints">Employee Posts API</a></td></tr><tr><td>Rate limits</td><td><a href="/api-introduction/rate-limits.md">Rate Limits</a></td></tr><tr><td>Credits</td><td><a href="/api-introduction/credits.md">Credits</a></td></tr></tbody></table>

## Employee Posts API endpoints

{% hint style="info" %}
Our API is a data retrieval tool. The endpoints do not support analytic features.
{% endhint %}

Employee Posts API features two search endpoints and one collect endpoints to retrieve employee posts data.\
Use the endpoints with any API-compatible application.

{% hint style="warning" %}
All Employee Posts API requests must be made over HTTPS. Requests made over HTTP will fail or be redirected to HTTPS.
{% endhint %}

Employee Posts API supports two types of requests:

* **Search** endpoints support POST requests only.
* **Collect** endpoints support GET requests only.

<table><thead><tr><th width="300.07421875">Endpoint</th><th width="299.8359375">Function</th><th>Credits</th></tr></thead><tbody><tr><td>POST <a href="/social-posts-data/employee-posts-api/search-filters.md"><em>/v2/employee_post/search/filter</em></a></td><td>Search for relevant employee posts files using search filters</td><td>Free</td></tr><tr><td>POST <a href="/social-posts-data/employee-posts-api/elasticsearch-dsl.md"><em>/v2/employee_post/search/es_dsl</em></a></td><td>An Elasticsearch DSL schema that maps directly to our output data.</td><td>Free</td></tr><tr><td>GET <a href="/social-posts-data/employee-posts-api/collect.md"><em>/v2/employee_post/collect/{post_id}</em></a></td><td>Convert the collected IDs to posts data</td><td>1</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/employee-posts-api.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.