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

# Get engagements modified after

> Get engagements that have been modified after a given point in time. Pass a Unix timestamp in milliseconds to start from a specific date, or pass a cursor returned by a previous response to continue from where you left off. Use this endpoint for incremental sync to efficiently retrieve only new and updated engagements without scanning your entire engagement history.

**Note:** Recently modified engagements may not appear immediately due to indexing delays.

**Note:** In addition to the contacts scope, the sales-email-read scope is required in order to receive the details of any email type engagements. See the Engagements overview for more details.



## OpenAPI

````yaml specs/legacy/v1/crm-engagements-v1.json GET /engagements/v1/engagements/modified/after
openapi: 3.0.0
info:
  title: CRM Engagements API v1
  version: 1.0.0
  description: Legacy CRM Engagements API v1 - Auto-generated from MDX documentation
servers:
  - url: https://api.hubapi.com
    description: HubSpot API Server
security: []
paths:
  /engagements/v1/engagements/modified/after:
    get:
      summary: Get engagements modified after
      description: >-
        Get engagements that have been modified after a given point in time.
        Pass a Unix timestamp in milliseconds to start from a specific date, or
        pass a cursor returned by a previous response to continue from where you
        left off. Use this endpoint for incremental sync to efficiently retrieve
        only new and updated engagements without scanning your entire engagement
        history.


        **Note:** Recently modified engagements may not appear immediately due
        to indexing delays.


        **Note:** In addition to the contacts scope, the sales-email-read scope
        is required in order to receive the details of any email type
        engagements. See the Engagements overview for more details.
      operationId: getengagementsv1engagementsmodifiedafter
      parameters:
        - name: after
          in: query
          required: false
          description: >-
            A Unix timestamp in milliseconds or a cursor returned by a previous
            response. Determines where to start reading from.
          schema:
            type: string
        - name: limit
          in: query
          required: false
          description: The number of records to return. Defaults to 100, maximum 1000.
          schema:
            type: integer
            maximum: 1000
      responses:
        '200':
          description: >-
            Successful response - Engagements modified after the specified
            cursor
          content:
            application/json:
              schema:
                type: object
                properties:
                  results:
                    type: array
                    items:
                      type: object
                  hasMore:
                    type: boolean
                  after:
                    type: string

````