> ## 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 website content changes

## Description

The **Company's Website Content Changes Enrichment** endpoint enables users to **track changes in website content over time**, helping businesses monitor **updates, keyword appearances, and messaging shifts**. This is particularly useful for **competitive intelligence, compliance tracking, and brand monitoring**.

The data includes:

* **Detection of content changes** in key sections of a company's website.
* **Keyword-based monitoring**, allowing users to track the appearance or disappearance of specific terms.
* **Timestamped records of detected modifications** to ensure historical tracking.
* **Logical AND search**: The system evaluates predefined conditions, ensuring that **all input keywords** must appear together in the retrieved snippets.

This information is sourced from **real-time web crawls and indexed website snapshots**, providing a **comprehensive view of content evolution over time**.

<AccordionGroup>
  <Accordion title="How It Works">
    * **Input:** Provide a `business_id` obtained from the **Match Businesses** API, along with optional `keywords` separated by commas. The system will return only results where **all keywords appear together**.
    * **Processing:** The system scans the target website and detects changes in text and keyword occurrences.
    * **Output:** A structured response highlighting updated content, extracted snippets, and relevant URLs.
  </Accordion>

  <Accordion title="Best Practices">
    * **Monitor competitors' websites** to track strategic updates and product announcements.
    * **Analyze keyword trends** to detect shifts in branding and messaging.
    * **Leverage historical data** to identify long-term content evolution and strategic priorities.
    * **Ensure regulatory compliance** by tracking content modifications in sensitive sectors.
    * **Use comma-separated keywords** to refine searches, ensuring that all specified terms appear together.
  </Accordion>

  <Accordion title="Website Changes Output Signal">
    | SignalAPI           | Name                            | Description                                                                                  | Data Type |
    | :------------------ | :------------------------------ | :------------------------------------------------------------------------------------------- | :-------- |
    | url                 | Website page of detected change | URL from which the changes were derived                                                      | url       |
    | change\_description | Type of content change          | Text describing the content modification on the website as compared to the previous version. | string    |
    | change\_implication | Description of content change   | Text indicating the strategic significance of the content change on the website              | string    |
    | date                | Content change timestamp        | Date the content change on the website occurred.                                             | 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/website_changes/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/website_changes/enrich:
    post:
      tags:
        - BusinessEnrichments
      summary: Website Changes
      operationId: businesses_website_changes_enrich
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BusinessesEnrichRequest'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/BusinessesEnrichResponse_WebsiteChangesOutputSchema_
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKeyHeader: []
        - APIKeyHeader: []
components:
  schemas:
    BusinessesEnrichRequest:
      properties:
        request_context:
          type: object
          title: Request Context
          example: null
          nullable: true
        parameters:
          type: object
          title: Parameters
          nullable: true
        business_id:
          type: string
          pattern: ^[a-f0-9]{32}$
          title: Business Id
      additionalProperties: false
      type: object
      required:
        - business_id
      title: BusinessesEnrichRequest
    BusinessesEnrichResponse_WebsiteChangesOutputSchema_:
      properties:
        response_context:
          $ref: '#/components/schemas/ResponseContext'
        data:
          anyOf:
            - $ref: '#/components/schemas/WebsiteChangesOutputSchema'
            - items:
                $ref: '#/components/schemas/WebsiteChangesOutputSchema'
              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[WebsiteChangesOutputSchema]
      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
    WebsiteChangesOutputSchema:
      properties:
        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: Url
        change_description:
          type: string
          title: Change Description
        change_implication:
          type: string
          title: Change Implication
        date:
          type: string
          format: date-time
          title: Date
      type: object
      title: WebsiteChangesOutputSchema
    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

````