Project assets are the defined lists of objects that can be attached to tasks within a project. You can query these assets to assist in constructing more precise Task queries.

Get Users

Use this endpoint to query the list of Users on a project.

Get Subcontractors

Use this endpoint to query the list of Subcontractors on a project.

Get Folders

Use this endpoint to query the tree of Folders on a project.

Get Packages

Use this endpoint to query the list of Packages on a project.

Get Calendars

Use this endpoint to query the list of Calendars on a project.

Get Locations

Use this endpoint to query the list of Locations on a project.

This endpoint provides access to the Work Areas on Published Plans for a project.

Teams generating plans utilising Map Space Locations generate a unique related dataset of real-world work areas and schedule tasks. Teams can use this location data in any of their external GIS or analytics tools with the Work Area API.

The Work Area API has three components.

This feature is in a closed beta phase and is available upon request only for Enterprise partners. Talk to us to learn more.

Overview

The foundation of the Aphex Planner data model are projects and tasks. Tasks reflect planned work and crucial properties such as subcontractors or shifts.

For customers and partners wanting to build external or internal applications and workflows on top of planned tasks, we provide a broad set of endpoints that give access to real-time data from a Plan workspace.

Typically use cases for these endpoints include;

• Third-party platforms and products building integrations to Aphex

• Internal customer teams using planned tasks as the trigger for internal apps or workflows

Our APIs follow the essence of REST and all queries must be made via HTTPS to pass the endpoint security rules.

Endpoints query rules and response structure can be accessed from the following page;

Project Tasks are the core object of Aphex Plan - this endpoint will return realtime Task data for a provided query.

Get Tasks

Use this endpoint to query Tasks on a project.

To generate a session token, you must provide a valid Client ID and Client Secret.

While in closed beta, you can obtain your API keys by contacting our Customer Success team.

Generate Token

Use this endpoint to generate a temporary Access Token

Revoke Token

Use this endpoint to revoke a previously generated Access token

Overview

This endpoint provides access to Published Plans for a project which can be a powerful way to establish a "cadence" based reporting routine (.e.g. comparing last week's performance against the prior week's) or the extraction and storage of historical plan data.

By accessing the Published Plans, you can ensure that any measurement of the data is based on reviewed and agreed plans by the project team.

The most common use cases of this endpoint are;

• connection to Aphex-provided Power BI templates.

• connection to Excel or Power BI to create custom-built reports across a project or series of projects.

• consumption and storage via an ETL operation across one or many projects within a portfolio.

The Power BI API has three components.

• Query Parameters

• Data Model

You can access the API by querying the endpoint URL for your desired project and providing a valid Token.

As a Project Administrator, head to your project in the Aphex Planner app. From the Integrations page the API can be enabled.

This will uncover the API URL specific to that project. The URL structure will be;

From the same location you sourced the API URL, a new Token created. Create a new Token and name it i.e. Project Dashboard Token 1

You cannot retrieve the token later so you should save it in a secret manager. If you lose the token you can generate a new one.

To successfully authenticate your request to the API URL, set the Token in the Authorization header of the request.

This can be done three ways;

1. If you are using an Aphex Power BI Template, simply paste the URL and Token into the setup modal

1. If you are generating your own report in Power BI, set up a new "Web" source. From within the Advanced menu enter the URL and header request key of Authorization with Bearer followed by your Token as the value.

1. If you are consuming the data in any other service construct a valid cURL request (example below).

Query parameters allow you to adjust what the response shall contain. To enable projects of varying size to get the most out of this API within the single response limit of 32Mb the following query parameters are supported;

Valid requests to the API will return a JSON response consistent with the API data model.

The Power BI API Data Model contains the following objects;

The Power BI API has a small number of restrictions and limits to ensure the availability of the system and the security of customer data.

• Token Management Restrictions: As covered in section, requests to the API will only succeed if they follow the correct request structure and include both a valid URL and Token. Tokens are generated individually for a Project, by a user with Project Admin rights.

• Token Validity Limits: Generated tokens have a maximum lifespan of 3 months to ensure that over time, project data is secure by default. On expiry, or at any time, new tokens can be generated for the project.

• Limits: To stay within infrastructure limits and avoid paged responses on this end point, a response limit of 32Mb exists. If you experience a server error, please try reducing you data request by passing in query parameters. There is also a hard data history limit of 6 months.