POST/api/v1/analysis/validate

Validate Schedule

Validate schedule for errors and warnings

DCMA logic validationGAO schedule quality

Request example

json

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

Request fields from OpenAPI contract

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
tasks	array<unknown>	Required	List of tasks in the schedule
tasks[].id	string	Required	Unique task identifier
start_task_ids	array<string>	Optional	Task IDs that anchor the project start (DCMA Check #1). If empty, tasks with no predecessors are treated as start tasks.
finish_task_ids	array<string>	Optional	Task IDs that anchor the project finish (DCMA Check #1). If empty, tasks with no successors are treated as finish tasks.
status_date	string \| null	Optional	Data date / status date for progress validation (ISO 8601 YYYY-MM-DD)
target_finish_date	string \| null	Optional	Target project finish date or key milestone date for CPLI calculation (ISO 8601)
baseline_approved_date	string \| null	Optional	Date when baseline was approved (for governance tracking)
resource_availability	array<unknown>	Optional	Per-resource availability for over-allocation detection (Resource Analysis API).
resource_availability[].resource_name	string	Optional	Resource name (must match tasks[*].resources)
resource_availability[].available_from	string \| null	Optional	Start of availability window (ISO 8601). Null = project start.
resource_availability[].available_to	string \| null	Optional	End of availability window (ISO 8601). Null = project finish.
resource_availability[].units_per_day	number	Optional	Available resource-units per working day (default: 1.0 = 100%)
options	object	Optional	Options for POST /api/v1/schedule/validate (v0.2.0).
options.calculate_pop	boolean	Optional	Calculate Probability of Performance (PoP) score (v0.2.0).
options.include_pop_details	boolean	Optional	Include dimensional PoP breakdown in response.
options.strict_mode	boolean	Optional	Treat warnings as errors (fail validation on any issue).
options.check_dcma_compliance	boolean	Optional	Include DCMA-specific checks (#1, #8).

Response example

json

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

Response fields from OpenAPI contract

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

Field	Type	Required	Description
status	string	Required	Top-level result status — always present in every response.
metadata	object	Required	Audit trail and processing context — always present, never null.
metadata.task_count	integer	Required	Number of tasks in the submitted schedule
metadata.endpoint	string	Required	Endpoint path e.g. /api/v1/health/score

Schema

json-schema

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

Authentication

API key required
x-api-key header

Reference details

Operation ID: analysis_validate
Section: Analysis
Tags: Analysis
Playground link: /playground?endpoint=/api/v1/analysis/validate&method=post

Was this page helpful?

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

Topic: Validate Schedule · Page: /docs/api-reference/analysis_validate

Report an issue Suggest improvement

Terms Privacy Contact

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