> ## Documentation Index > Fetch the complete documentation index at: https://docs.sixtyfour.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Latest Changes > Each row's latest change time per watched field, as `{row_id: {field: timestamp}}` (ISO 8601). Only `change` events count; rows and fields with no change are left out, and an empty history returns `{}`. ## OpenAPI ````yaml https://api.sixtyfour.ai/openapi.json get /monitors/{monitor_id}/changes openapi: 3.1.0 info: title: Sixtyfour API description: >- Intelligence API for people and companies: research agents that investigate, resolve identities, map relationships and surface risk signals. contact: name: Sixtyfour url: https://sixtyfour.ai/ email: support@sixtyfour.ai license: name: Proprietary version: 1.0.0 servers: - url: https://api.sixtyfour.ai description: Production security: - ApiKeyAuth: [] - BearerAuth: [] tags: - name: Enrichment description: Find and enrich emails, phones, and LinkedIn for people and companies. - name: Search description: Run deep and filter searches over Sixtyfour's data. - name: Workflow description: Create, run, and manage enrichment workflows. - name: Workflow Schedules description: Create and manage recurring schedules for workflows. - name: Account description: Manage and inspect your account and credit balance. - name: Intelligence description: Verify identity attributes such as age using high-tier OSINT research. - name: Atlas description: >- Start, continue and read Atlas investigations: attribution graph, workspace files, reports and exports. paths: /monitors/{monitor_id}/changes: get: tags: - Monitors summary: List Latest Changes description: >- Each row's latest change time per watched field, as `{row_id: {field: timestamp}}` (ISO 8601). Only `change` events count; rows and fields with no change are left out, and an empty history returns `{}`. operationId: monitor_changes_endpoint_monitors__monitor_id__changes_get parameters: - name: monitor_id in: path required: true schema: type: string title: Monitor Id responses: '200': description: Successful Response content: application/json: schema: type: object additionalProperties: additionalProperties: type: string type: object title: >- Response Monitor Changes Endpoint Monitors Monitor Id Changes Get '400': description: Invalid request. content: application/json: schema: properties: detail: type: string code: type: string description: Stable error code, for programs. correlation_id: type: string description: >- This request's ID, also in `X-Correlation-ID`. Quote it to support. type: object example: detail: Invalid request body code: bad_request correlation_id: enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21 '401': description: Missing or invalid API key. content: application/json: schema: properties: detail: type: string code: type: string description: Stable error code, for programs. correlation_id: type: string description: >- This request's ID, also in `X-Correlation-ID`. Quote it to support. type: object example: detail: Invalid API key code: unauthenticated correlation_id: enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21 '403': description: Organization access is locked. content: application/json: schema: properties: detail: type: string code: type: string description: Stable error code, for programs. correlation_id: type: string description: >- This request's ID, also in `X-Correlation-ID`. Quote it to support. type: object example: detail: >- This organization no longer has access to Sixtyfour. Contact your representative at Sixtyfour. code: forbidden correlation_id: enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21 '422': description: Invalid request fields or monitor input. content: application/json: schema: $ref: '#/components/schemas/MonitorValidationErrorResponse' '500': description: Unexpected server error. Retry with backoff. content: application/json: schema: properties: detail: type: string code: type: string description: Stable error code, for programs. correlation_id: type: string description: >- This request's ID, also in `X-Correlation-ID`. Quote it to support. type: object example: detail: Internal server error code: internal_error correlation_id: enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21 '503': description: >- Temporarily unavailable. Nothing was charged; retry after the `Retry-After` header. content: application/json: schema: properties: detail: type: string code: type: string description: Stable error code, for programs. correlation_id: type: string description: >- This request's ID, also in `X-Correlation-ID`. Quote it to support. type: object example: detail: Could not verify the API key right now. Retry shortly. code: unavailable correlation_id: enrich_3f8b2c1e-9d4a-4c1b-8e2f-6a7b5c4d3e21 components: schemas: MonitorValidationErrorResponse: properties: detail: anyOf: - type: string - items: $ref: '#/components/schemas/MonitorValidationErrorItem' type: array title: Detail code: type: string description: Stable error code, for programs. correlation_id: type: string description: This request's ID, also in `X-Correlation-ID`. Quote it to support. type: object required: - detail title: MonitorValidationErrorResponse description: Field validation errors and monitor input errors. MonitorValidationErrorItem: properties: loc: items: anyOf: - type: string - type: integer type: array title: Loc description: Path to the invalid field examples: - - body - name msg: type: string title: Msg description: Human-readable error message examples: - Field required type: type: string title: Type description: Validation error code examples: - missing input: title: Input ctx: anyOf: - additionalProperties: true type: object - type: 'null' title: Ctx type: object required: - loc - msg - type title: MonitorValidationErrorItem description: A validation error, with the path of the field it concerns. securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: Your Sixtyfour API key. BearerAuth: type: http scheme: bearer description: >- An OAuth access token from `POST /oauth/token`, sent as `Authorization: Bearer `. An API key sent as a bearer token is refused with 401. When both headers are sent, the bearer token is used. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.