Acuity PPM API

2026-10-08

Added the Power BI setup guide for company enablement, Desktop connection, and Service refresh.
Added a dataset catalog, financial modeling guidance, BI OData/JSON/CSV reference, and troubleshooting.
Documented company-token access, cached export freshness, gateway requirements for Basic OData authentication, and unsupported OData query options.
Self-service instructions follow the current implementation source. Availability depends on the Acuity version in your environment.
Consolidated the guide into three concise pages: setup, datasets and modeling, and API reference with error fixes.

Documented categorized NPT rows with npt_category_id and npt_category_name, category allocations and period overrides, and effective zero values outside resource availability.
Added npt_category_id to the NPT deduplication key so separate categories are retained when combining project and proposal snapshots.
Added residual_priority, residual_severity, and residual_likelihood to risk response schemas and examples.
Documented strict timeline dates, HTTP 400, 422, and 204, and converted-proposal rejection. Timeline pages now display response tabs.
Documented decimal-string numeric custom fields for project/proposal creation, updates, and responses.
This update aligns the portal with the Acuity staging source checked on 2026-10-08. It does not establish endpoint availability in every customer environment.

Added snapshot_source to GET /api/snapshot/projects/resources and GET /api/snapshot/proposals/resources.
snapshot_source is projects for project resource rows and proposals for proposal resource rows.
Both endpoints use the same normalized row contract: one resource/time-period cell per JSON object.
When combining project and proposal resource snapshots, filter or deduplicate overlapping non_project_work cells by work_type, resource_id, npt_category_id, fiscal_year, and period_number to avoid double-counting NPT. The category key was added to this guidance on 2026-10-08.

Changed GET /api/snapshot/projects/resources and GET /api/snapshot/proposals/resources from wide rows with period-label columns to a normalized fact/cell response.
Each JSON object now represents exactly one resource and one time period.
Added stable period fields: period, period_name, period_number, fiscal_year, and estimate.
estimate now contains the period cell value: project/proposal work for project_work rows and non-project time for non_project_work rows.
Added work_type with project_work for project/proposal assignment allocation and non_project_work for non-project-time allocation.
Removed period-label keys from the response shape.
resource_department was replaced by resource_team. resource_team is included only when company resource team hierarchy is enabled.
period_start_date and period_end_date are not included.
The new stable-column format is intended for Excel pivot tables and Power BI.

Added GET /api/snapshot/projects/scores and GET /api/snapshot/proposals/scores.
Both endpoints return a flat score matrix for Excel, BI, and Gantt-style reporting.
Each response row represents one project/proposal and one company scoring criterion.
Missing or unselected criteria are still returned, with scoring_criterion_option_* fields set to null.
Added project_type, score_category, criterion metadata, selected option metadata, and last_updated fields to the documented schema.
GET /api/snapshot/projects/scores returns active project score rows.
GET /api/snapshot/proposals/scores returns proposal score rows. Approved proposals that have already moved into active project stage belong to project data.

Flattened GET-only sections so they appear directly under Projects or Proposals.
Kept separate grouped sections only where multiple record endpoints exist, such as Project, Task, Proposal, and Status Report.

Added proposal list, retrieve, create, update, timeline, milestones, and resources pages.
Started aligning proposal examples and schema with the currently verified live API behavior.