The ILAP Analytics API lets you consume scheduling data — schedules, activities, periodized progress, resources, links, and metadata — for reporting and integration. This overview is for planners and Power BI / report developers, as well as data engineers, and assumes REST/GraphQL basics and that you can obtain a DataReader token.
What data is available
- Schedules & revisions
- Activities (+ periodized planned/earned/actual hours)
- Successors/links
- Resource assignments
- Calendars
- Metadata fields
Tenant-specific extension fields appear dynamically on GraphQL types and are not enumerated here.
Revision types
Live— the current working version of the schedule.Baseline— the version most recently set as the baseline for comparison.OriginalBaseline— the first baseline ever set, preserved for original-plan comparisons.Current— the latest revision regardless of baseline status.
REST export vs GraphQL — when to use which
REST export (/api/v3/export/*) |
GraphQL (/graphql) |
|
|---|---|---|
| Shape | Fixed, tabular, IDE-compatible | You pick exactly the fields |
| Paging | PageNumber + PageSize |
Cursor (first/after) |
| Best for | Full/bulk extracts into a Lakehouse/Warehouse (Fabric) | Targeted, filtered queries & progress summaries (Power BI) |
| Filtering | By ReportScheduleId + RevisionType |
where / order + projection |
Authentication
All API calls require a bearer token scoped to the DataReader role. See the Authentication guide for how to request and use one.
Guides
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article