Explanation and Concepts

For a quick introduction to concepts and usage, visit the ProjectSight Basics documentation.

Terms

The following are a few terms to become familiar with as they relate to using ProjectSight APIs:

• Portfolio - A top level entity, portfolios are collections of projects and the settings that those projects share. Get this first to manage projects
• Projects - Each project entity represents a construction project
• Records - ProjectSight supports many unique record types, which relate to the business processes that they are used to manage. These include RFIs, Submittals, Contracts, Change Orders, and many more

Dependencies

• You must be an authorized user in order to access ProjectSight data via the API (subscribing to this API will kick off this process with the ProjectSight team)
• In order to create new Portfolios, you must be a Portfolio Administrator for at least one other Portfolio that has an active license for ProjectSight. Contact your administrator or ProjectSight support if you need to request this level of access
• You must log into ProjectSight at least once prior to being allowed to establish a connection via the API