# Company Activities Endpoints

These endpoints let you explore a company’s **public activity**: the posts it publishes, and the engagement around those posts (comments, reactions, reposts). Use them to power **account research, competitor monitoring, content analytics, and ABM signals**.

***

### 1) Company Posts

Retrieve recent **posts** (activity updates) published by a company based on its Social URL (or equivalent identifier).

| Aspect       | Description                                                                                   |
| ------------ | --------------------------------------------------------------------------------------------- |
| **Purpose**  | Get the public posts published by a company.                                                  |
| **Input**    | `socialUrl` (company’s Social page URL) — required. Optional `page` parameter for pagination. |
| **Output**   | A list of **post objects** + metadata (pagination, credits, rate limits).                     |
| **Credits**  | 1 credit per successful call.                                                                 |
| **Best for** | Account research, content strategy, competitor monitoring.                                    |

#### 🧩 Objects Structure (post)

* `activityId` — unique identifier of the post
* `text` — textual content of the post
* `reactionsCount`, `commentsCount` — engagement counters
* `activityDate` — timestamp of publication
* `author` — object with `authorId`, `authorName`, `authorPublicIdentifier`, `authorHeadline`, `authorImage`, `authorUrl`
* `activityUrl` — Social URL of the post
* `shareUrl` — shareable link to the post
* `metadata` — pagination info: `currentPage`, `pageNumber`, `perPage`, `total`

***

### 2) Company Post

Retrieve **detailed data for one specific post** of a company, given its `activityId` or Social URL.

| Aspect       | Description                                                                       |
| ------------ | --------------------------------------------------------------------------------- |
| **Purpose**  | Get full details of a single company post.                                        |
| **Input**    | `activityId` (the post’s ID) — required.                                          |
| **Output**   | A **post object** with full details.                                              |
| **Credits**  | 1 credit per request.                                                             |
| **Best for** | Detailed post analytics, linking to sub-endpoints (comments, reactions, reposts). |

#### 🧩 Objects Structure (post)

* `activityId`
* `text`
* `reactionsCount`, `commentsCount`
* `activityDate`
* `author` (with identity fields)
* `activityUrl`, `shareUrl`
* `relatedPost` — optional, if it’s a reshared post

***

### 3) Post Comments

Retrieve **all comments** made on a specific company post.

| Aspect       | Description                                                          |
| ------------ | -------------------------------------------------------------------- |
| **Purpose**  | See the conversation under a specific post.                          |
| **Input**    | `activityId` (post’s ID) — required. Optional `page` for pagination. |
| **Output**   | A list of **comment objects** + metadata.                            |
| **Credits**  | 1 credit per call/page.                                              |
| **Best for** | Engagement analysis, sentiment tracking, community insights.         |

#### 🧩 Objects Structure (comment)

* `text` — content of the comment
* `reactionsCount` — number of reactions on the comment
* `commentsCount` — number of replies under the comment
* `activityDate` — timestamp of the comment
* `author` — object with `authorId`, `authorName`, `authorPublicIdentifier`
* `activityUrl` — Social URL of the comment

***

### 4) Post Reactions

Retrieve the **reactions** on a specific company post — who reacted and what type of reaction.

| Aspect       | Description                                                          |
| ------------ | -------------------------------------------------------------------- |
| **Purpose**  | Understand which users engaged with the post and how.                |
| **Input**    | `activityId` (post’s ID) — required. Optional `page` for pagination. |
| **Output**   | A list of **reaction objects** + metadata.                           |
| **Credits**  | 1 credit per call/page.                                              |
| **Best for** | Audience mapping, engagement tracking, campaign analytics.           |

#### 🧩 Objects Structure (reaction)

* `type` — type of reaction (e.g., LIKE)
* `author` — object with `authorId`, `authorName`, `authorUrl`

***

### 5) Post Reposts

Retrieve the **reposts (shares)** of a company post — who reshared it and when.

| Aspect       | Description                                                          |
| ------------ | -------------------------------------------------------------------- |
| **Purpose**  | Measure amplification and reach of company content.                  |
| **Input**    | `activityId` (post’s ID) — required. Optional `page` for pagination. |
| **Output**   | A list of **repost objects** + metadata.                             |
| **Credits**  | 1 credit per call/page.                                              |
| **Best for** | Virality analysis, campaign measurement, influencer mapping.         |

#### 🧩 Objects Structure (repost)

* `activityDate` — timestamp of the repost
* `author` — object with `authorId`, `authorName`, `authorPublicIdentifier`
* `activityUrl` — Social URL of the repost
* `commentary` — optional text added by the reposter

{% hint style="warning" %}
**Important Notice**

This documentation is only a **preview** of our API. It provides a high-level overview of what the API can do and which types of data objects you can expect.\
\
The **official API Reference** — including full technical specifications, JSON schemas, sample results, error codes, and authentication details — is only available after signing up to our platform.\
\ <a href="https://app.scrapin.io/auth/register" class="button primary">Sign up to access the full API Reference</a>
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.scrapin.io/api/readme-6.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
