01
Documented
P6 EPPM REST API
Oracle documents REST resources for projects, EPS, resources, relationships, jobs, and other P6 entities.
Oracle / Project planning and scheduling
Evaluate Primavera P6 by deployed product and release, EPS and project scope, calendar and coding standards, schedule authority, REST/API availability, and the professional controls governing schedule changes.
What it is designed to do
Planning, scheduling, resource, progress, and portfolio structures for project and programme controls in configured Primavera P6 environments.
Best suited for
Project controls teams managing detailed schedules, activity relationships, resources, calendars, baselines, and controlled schedule updates.
Buyer boundary
This profile explains documented product and integration surfaces. It is not an endorsement, procurement recommendation, guarantee of compatibility, or substitute for checking the buyer’s product, edition, region, licences, configuration, terms, permissions, and workflow.
Normal operating records
P6 may remain authoritative for the accepted schedule and its controlled structures. A dashboard extract, spreadsheet, data warehouse, AI summary, or field update is not automatically an accepted schedule revision.
Typical AEC uses
Records and information
EPS and project
WBS and activity
Activity relationship
Calendar
Resource and assignment
Baseline, code, UDF, and schedule job where configured
Documented access routes
A vendor interface establishes a possible technical route. It does not establish record authority, downstream security, correct mapping, complete processing, accepted output, or permission to act.
Documented
Oracle documents REST resources for projects, EPS, resources, relationships, jobs, and other P6 entities.
Product-dependent
Available interfaces depend on the deployed P6 product, release, hosting model, configuration, and licences.
Product-dependent
XER, XML, spreadsheet, report, or database-derived exchange may be used under approved schedule-control procedures.
Not primary
The official sources reviewed establish REST access but do not justify presenting P6 as a generally webhook-native system.
Native IDs and crosswalks
Identity, permission, and authority
Known implementation limits
Match the integration to the installed P6 release and environment. Do not design from current cloud documentation when the buyer operates an older on-premises deployment without confirming supported interfaces and upgrade constraints.
Interfaces and fields differ by P6 product and release
ObjectId values are environment-specific and need controlled crosswalks
Running a schedule job does not establish acceptance of the result
Field progress, forecast, and schedule logic require reconciliation and professional review
Where StructuredLayer may connect it
The actual implementation boundary is confirmed from the buyer's product, workflow, records, permissions, difficult cases, required direction, consequences, and acceptance conditions.
Crosswalk project, WBS, activity, resource, and relationship IDs
Connect approved field evidence and constraints without directly accepting schedule changes
Build schedule-to-field review queues
Reconcile dashboard measures to the accepted schedule extract
Preserve schedule version, data date, and approval state
Questions before scope
Which P6 product, release, and hosting model are deployed?
Which EPS, projects, baselines, calendars, and codes are in scope?
Who owns schedule updates and acceptance?
Is read-only reporting sufficient?
How are field progress and forecast changes reconciled?
Official vendor documentation
Features, endpoints, scopes, licences, regions, plans, limits, and vendor terms can change. The implementation must confirm the current documentation for the buyer's actual environment.
Related system profiles
Primary operating system
Project execution and construction records
Inspect profilePrimary operating system
Document libraries, lists, mail, collaboration, and identity context
Inspect profilePrimary operating system with 2026 product-name transition
Document, model, design-collaboration, takeoff, and construction-project context
Inspect profileOracle Primavera P6 and one workflow
Bring the exact product, module, environment, workflow, records, users, permissions, required access direction, current failure, and intended buyer decision.
Next best page
Move from evaluating the operating conditions to choosing a bounded response and assessing one real workflow.