> ## 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.

# Workforce trends by company department (Bulk)

<AccordionGroup>
  <Accordion title="How It Works">
    * **Input:** Provide a list of up to **`50business_ids`**.
    * **Processing:** The system retrieves workforce trends data for all submitted businesses in a **single request**.
    * **Output:** A structured response with workforce distribution and hiring/firing trends.
  </Accordion>

  <Accordion title="Example Request (cURL)">
    ```shell Bash theme={null}
    curl --request POST \
         --url https://api.explorium.ai/v1/businesses/workforce_trends/bulk_enrich \
         --header 'accept: application/json' \
         --header 'api_key: your_api_key_here' \
         --header 'content-type: application/json' \
         --data '{
      "business_ids": [
        "8adce3ca1cef0c986b22310e369a0793",
        "a34bacf839b923770b2c360eefa26748"
      ]
    }'
    ```
  </Accordion>

  <Accordion title="Best Practices">
    * **Monitor hiring trends** to identify workforce expansion.
    * **Assess downsizing activity** to evaluate business contraction.
    * **Benchmark workforce trends** against industry peers.
  </Accordion>
</AccordionGroup>

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

## Body Params - Try Me Example

```
business_ids: ["8adce3ca1cef0c986b22310e369a0793",
               "a34bacf839b923770b2c360eefa26748"]
```


## OpenAPI

````yaml post /v1/businesses/workforce_trends/bulk_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/workforce_trends/bulk_enrich:
    post:
      tags:
        - BulkBusinessEnrichments
      summary: Workforce Trends
      operationId: businesses_workforce_trends_bulk_enrich
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BusinessesBulkEnrichRequest'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/BusinessesBulkEnrichResponse_WorkforceTrendsOutputSchema_
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKeyHeader: []
        - APIKeyHeader: []
components:
  schemas:
    BusinessesBulkEnrichRequest:
      properties:
        request_context:
          type: object
          title: Request Context
          example: null
          nullable: true
        parameters:
          type: object
          title: Parameters
          nullable: true
        business_ids:
          items:
            type: string
            pattern: ^[a-f0-9]{32}$
          type: array
          maxItems: 50
          minItems: 1
          title: Business Ids
      additionalProperties: false
      type: object
      required:
        - business_ids
      title: BusinessesBulkEnrichRequest
    BusinessesBulkEnrichResponse_WorkforceTrendsOutputSchema_:
      properties:
        response_context:
          $ref: '#/components/schemas/ResponseContext'
        data:
          items:
            $ref: >-
              #/components/schemas/BusinessesBulkEnrichRow_WorkforceTrendsOutputSchema_
          type: array
          title: Data
        entity_id:
          anyOf:
            - type: string
              pattern: ^[a-f0-9]{32}$
            - type: string
              pattern: ^[a-f0-9]{40}$
          title: Entity Id
        total_results:
          type: integer
          title: Total Results
      type: object
      required:
        - response_context
        - total_results
      title: BusinessesBulkEnrichResponse[WorkforceTrendsOutputSchema]
      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
    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
    BusinessesBulkEnrichRow_WorkforceTrendsOutputSchema_:
      properties:
        business_id:
          type: string
          pattern: ^[a-f0-9]{32}$
          title: Business Id
        data:
          $ref: '#/components/schemas/WorkforceTrendsOutputSchema'
      type: object
      required:
        - business_id
      title: BusinessesBulkEnrichRow[WorkforceTrendsOutputSchema]
    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.
    WorkforceTrendsOutputSchema:
      properties:
        change_in_real_estate_roles:
          type: number
          title: Change In Real Estate Roles
        perc_design_roles:
          type: number
          title: Perc Design Roles
        profiles_found_per_quarter:
          type: number
          title: Profiles Found Per Quarter
        perc_sales_roles:
          type: number
          title: Perc Sales Roles
        perc_hr_roles:
          type: number
          title: Perc Hr Roles
        perc_operations_roles:
          type: number
          title: Perc Operations Roles
        perc_pr_roles:
          type: number
          title: Perc Pr Roles
        perc_health_roles:
          type: number
          title: Perc Health Roles
        perc_trades_roles:
          type: number
          title: Perc Trades Roles
        perc_engineering_roles:
          type: number
          title: Perc Engineering Roles
        perc_finance_roles:
          type: number
          title: Perc Finance Roles
        perc_customer_service_roles:
          type: number
          title: Perc Customer Service Roles
        perc_legal_roles:
          type: number
          title: Perc Legal Roles
        perc_media_roles:
          type: number
          title: Perc Media Roles
        perc_marketing_roles:
          type: number
          title: Perc Marketing Roles
        perc_real_estate_roles:
          type: number
          title: Perc Real Estate Roles
        perc_education_roles:
          type: number
          title: Perc Education Roles
        change_in_design_roles:
          type: number
          title: Change In Design Roles
        change_in_education_roles:
          type: number
          title: Change In Education Roles
        change_in_pr_roles:
          type: number
          title: Change In Pr Roles
        change_in_trades_roles:
          type: number
          title: Change In Trades Roles
        change_in_customer_service_roles:
          type: number
          title: Change In Customer Service Roles
        change_in_health_roles:
          type: number
          title: Change In Health Roles
        change_in_operations_roles:
          type: number
          title: Change In Operations Roles
        change_in_sales_roles:
          type: number
          title: Change In Sales Roles
        change_in_legal_roles:
          type: number
          title: Change In Legal Roles
        change_in_roles_divisor:
          type: number
          title: Change In Roles Divisor
        change_in_finance_roles:
          type: number
          title: Change In Finance Roles
        change_in_media_roles:
          type: number
          title: Change In Media Roles
        change_in_hr_roles:
          type: number
          title: Change In Hr Roles
        change_in_marketing_roles:
          type: number
          title: Change In Marketing Roles
        change_in_engineering_roles:
          type: number
          title: Change In Engineering Roles
        quarters:
          type: string
          format: date-time
          title: Quarters
      type: object
      title: WorkforceTrendsOutputSchema
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: api_key

````