POST/api/v1/forensics/change-tracking/async

Time-Series Change Detection (Async)

Submit async change tracking for large schedules. Poll GET /api/v1/jobs/{job_id}.

Request example

json

{
  "tasks": [
    {
      "id": "T1",
      "duration_days": 5
    }
  ]
}

Required fields and the optional fields that change this call are listed here. The shared task model stays on the task schema guide.

This table is generated from the endpoint schema in openapi.json.

Field	Type	Required	Description
current_schedule	object	Required	The current schedule submitted for change tracking comparison.
current_schedule.tasks	array<unknown>	Required	Current task array
current_schedule.tasks[].id	string	Required	Unique task identifier
current_schedule.status_date	string	Required	Current schedule status date (ISO 8601)
schedule_history	array<unknown>	Required	Historical snapshots (min 1 required)
schedule_history[].snapshot_date	string	Required	Snapshot date (ISO 8601 YYYY-MM-DD)
schedule_history[].tasks	array<unknown>	Required	Task array at snapshot time
schedule_history[].tasks[].id	string	Required	Unique task identifier
options	object	Optional	Options controlling change tracking behaviour.
options.comparison_mode	string	Optional	No description in OpenAPI contract.
options.change_categories	array<string>	Optional	Categories: baseline, actual, forecast, logic, resource, progress, all
options.include_impact_analysis	boolean	Optional	No description in OpenAPI contract.
options.include_trends	boolean	Optional	No description in OpenAPI contract.
options.include_details	boolean	Optional	No description in OpenAPI contract.
options.materiality_thresholds	object	Optional	Overridable materiality thresholds for change detection.
options.materiality_thresholds.date_change_days	integer	Optional	Min days for a date change to be material
options.materiality_thresholds.progress_change_pct	number	Optional	Min % decrease to flag

json

{
  "score": 92,
  "grade": "A"
}

json-schema

{
  "$ref": "#/components/schemas/ChangeTrackingRequest"
}

Operation ID: change_tracking_async_api_v1_forensics_change_tracking_async_post
Section: Forensics
Tags: Forensics
Playground link: /playground?endpoint=%2Fapi%2Fv1%2Fforensics%2Fchange-tracking%2Fasync&method=post

Was this page helpful?

Your feedback helps us improve docs, reference pages, and Playground flows.

Topic: Time-Series Change Detection (Async) · Page: /docs/api-reference/change_tracking_async_api_v1_forensics_change_tracking_async_post

Schedule analysis guidance. Not legal advice. You remain responsible for contract and agency compliance.