Import

Import Primavera P6 XER Schedule

Parses a Primavera P6 XER file and returns a Normalized Schedule JSON object compatible with all analysis APIs.

Tier access: Starter and above.

File size limit: 100 MB.

Input: XER file content as a UTF-8 or Latin-1 string in the file_content field.

Multi-project XER: If the XER file contains multiple projects, specify options.project_id to select the target project. Omitting project_id when multiple projects are present returns a 422 error listing available project IDs.

Output: normalized_schedule (ready to submit to /health/score, /forensics/dcma-14-point, etc.) plus parse_summary, mapping_stats, warnings, and processing_metadata.

post/api/v1/import/xer

Request

Base URL: https://api.bellatorsi.com (the document declares no server; this is the origin it was published from)
URL: https://api.bellatorsi.com/api/v1/import/xer
Auth: none declared

Headers

x-api-keystring nullable

authorizationstring nullable

x-bellator-internal-dispatchstring nullable

Request body

file_contentstring required

P6 XER file content (text, any encoding — auto-detected)

Response

Schedule successfully parsed and normalized

status'pass' | 'fail' | 'warning' | 'info' required

Top-level result status — always present in every response.

scorenumber nullable

grade'A' | 'B' | 'C' | 'D' | 'F'

Letter grade derived from a 0–100 score. Null on non-scoring endpoints.

summarystring nullable

breakdownobject nullable

Example response

{
  "data": {
    "normalized_schedule": {
      "tasks": [
        {
          "duration_days": 10,
          "id": "T1",
          "name": "Design Phase",
          "percent_complete": 0,
          "planned_finish": "2026-01-15",
          "planned_start": "2026-01-01",
          "predecessors": [],
          "resource": "Team A"
        }
      ]
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.