> ## Documentation Index
> Fetch the complete documentation index at: https://developers.explorium.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Company’s social media presence

## Description

The **Company's Social Media Presence Enrichment** endpoint provides insights into a company's **Social media activity, engagement trends, and posting behavior**. This dataset is valuable for **brand analysts, marketers, and business strategists** looking to assess **corporate communication trends and social media reach**.

The data includes:

* **Volume of Social media posts** over a given period.
* **Engagement metrics**, such as likes, shares, and comments.
* **Trending topics and key themes** in company communications.

This information is sourced from **public Social media data and corporate social media feeds** to offer a **comprehensive view of a company's digital engagement and brand presence**.

<AccordionGroup>
  <Accordion title="How It Works">
    * **Input:** Provide a `business_id` obtained from the **Match Businesses** API.
    * **Processing:** The system retrieves Social media activity, post frequency, and engagement trends.
    * **Output:** A structured response summarizing social media presence and key engagement metrics.
  </Accordion>

  <Accordion title="Best Practices">
    * **Use social media insights** to track brand perception and digital engagement trends.
    * **Analyze posting behavior** to understand a company's content strategy and outreach.
    * **Leverage engagement data** to benchmark a company's influence against competitors.
    * **Monitor trending topics** to gain insights into corporate priorities and industry focus.
  </Accordion>

  <Accordion title="Company's Social Media Presence Output Signal">
    | SignalAPI            | Name                    | Description                                                        | Data Type |
    | :------------------- | :---------------------- | :----------------------------------------------------------------- | :-------- |
    | post\_text           | Post text content       | Text content of the LinkedIn® post published by company profile.   | string    |
    | days\_since\_posted  | Days since post         | Number of days since the post was published by the company.        | integer   |
    | post\_url            | LinkedIn® post URL      | URL to the LinkedIn® post published by individual.                 | url       |
    | number\_of\_comments | Number of post comments | Number of comments on the company's post by time of collection.    | integer   |
    | number\_of\_likes    | Number of post likes    | Number of likes the company's post received by time of collection. | integer   |
    | created\_at          | Time of posting         | Timestamp of when the company's post was published.                | datetime  |
  </Accordion>
</AccordionGroup>

<Icon icon="thumbtack" iconType="solid" color="red" /> For additional enrichment options, explore related API endpoints below.

## Body Params - Try Me Example

```
business_id: 8adce3ca1cef0c986b22310e369a0793
```


## OpenAPI

````yaml post /v1/businesses/linkedin_posts/enrich
openapi: 3.1.0
info:
  title: Partner Service
  version: 0.2.349
servers:
  - url: https://api.explorium.ai
    description: AgentSource Server
security: []
paths:
  /v1/businesses/linkedin_posts/enrich:
    post:
      tags:
        - BusinessEnrichments
      summary: Linkedin Posts
      operationId: businesses_linkedin_posts_enrich
      requestBody:
        content:
          application/json:
            schema:
              $ref: >-
                #/components/schemas/partner_service__models__businesses__enrich_requests__LinkedInPostsEnrichRequest
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/BusinessesEnrichResponse_LinkedinCompaniesPostsOutputSchema_
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKeyHeader: []
        - APIKeyHeader: []
components:
  schemas:
    partner_service__models__businesses__enrich_requests__LinkedInPostsEnrichRequest:
      properties:
        request_context:
          type: object
          title: Request Context
          example: null
          nullable: true
        parameters:
          $ref: '#/components/schemas/LinkedInPostsEnrichmentParams'
        business_id:
          type: string
          pattern: ^[a-f0-9]{32}$
          title: Business Id
      additionalProperties: false
      type: object
      required:
        - business_id
      title: LinkedInPostsEnrichRequest
    BusinessesEnrichResponse_LinkedinCompaniesPostsOutputSchema_:
      properties:
        response_context:
          $ref: '#/components/schemas/ResponseContext'
        data:
          anyOf:
            - $ref: '#/components/schemas/LinkedinCompaniesPostsOutputSchema'
            - items:
                $ref: '#/components/schemas/LinkedinCompaniesPostsOutputSchema'
              type: array
          title: Data
        entity_id:
          anyOf:
            - type: string
              pattern: ^[a-f0-9]{32}$
            - type: string
              pattern: ^[a-f0-9]{40}$
          title: Entity Id
      type: object
      required:
        - response_context
      title: BusinessesEnrichResponse[LinkedinCompaniesPostsOutputSchema]
      description: 'This is base response model for all responses in partner service. '
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    LinkedInPostsEnrichmentParams:
      properties: {}
      additionalProperties: false
      type: object
      title: LinkedInPostsEnrichmentParams
    ResponseContext:
      properties:
        correlation_id:
          type: string
          title: Correlation Id
        request_status:
          $ref: '#/components/schemas/RequestStatus'
        time_took_in_seconds:
          type: number
          title: Time Took In Seconds
      type: object
      required:
        - correlation_id
        - request_status
        - time_took_in_seconds
      title: ResponseContext
    LinkedinCompaniesPostsOutputSchema:
      properties:
        display_name:
          type: string
          title: Display Name
        post_text:
          type: string
          title: Post Text
        days_since_posted:
          type: integer
          title: Days Since Posted
        post_url:
          type: string
          maxLength: 2048
          pattern: >-
            ^(https?:)?//(?:(?:[a-z0-9\u00a1-\uffff][a-z0-9\u00a1-\uffff_-]{0,62})?[a-z0-9\u00a1-\uffff]\.)+[a-z\u00a1-\uffff]{2,}\.?(?:[/?#]\S*)?$
          format: uri
          title: Post Url
        number_of_comments:
          type: integer
          title: Number Of Comments
        number_of_likes:
          type: integer
          title: Number Of Likes
        created_at:
          type: string
          format: date-time
          title: Created At
      type: object
      title: LinkedinCompaniesPostsOutputSchema
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
    RequestStatus:
      type: string
      enum:
        - success
        - miss
        - failure
      title: RequestStatus
      description: >-
        The `RequestStatus` class is an enumeration that defines the possible
        statuses of a request.


        This enum is used to indicate whether a request was successful, missed,
        or failed. It ensures

        consistent handling of request statuses across the application.


        Attributes:
            SUCCESS: Indicates that the request was successfully processed.
            MISS: Indicates that the request did not find any matching data.
            FAILURE: Indicates that the request encountered an error or failure.
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: api_key

````