Introduction to the Project Connect API

Introduction to the Project Connect API


The Project Connect API is a secure and structured way for customers to connect their own systems directly to DNV Project Connect. It allows applications to access selected project information without having to work through the user interface.


The API is built as a set of REST web services and is designed to be customer oriented and easy to integrate. It exposes the same core data that customers already see in Project Connect, because Project Connect itself uses this very same API.

What can the Project Connect API be used for?

With the Project Connect API, applications can:

  • Retrieve information about projects
  • Access documents and document metadata
  • Read and respond to comments
  • Upload documents to projects

This makes it possible to integrate Project Connect data into customer systems, dashboards, or workflows, while keeping access controlled and secure.

How does authentication work?

To use the API, access is managed through Veracity, DNV’s identity and access platform.


At least one developer must register both themselves and their application in Veracity. All users who will access data through the API must have:


Veracity handles authentication using modern security standards, including multi factor authentication and OpenID Connect. Access tokens issued by Veracity are used when calling the API.


These are the same user accounts customers already use for Project Connect, which ensures a consistent and secure access model.

How is access to project data controlled?

Having access to the API does not automatically give access to project data.


Each user must be explicitly added to a project by the responsible DNV project manager. If a user is not assigned to a project, the API can still be called, but it will not return any project data.


This ensures that users only see information they are authorized to access.


Once access is set up and the user is assigned to a project, the API can be used immediately to exchange information for those projects.

Requesting access to the API

Access to the Project Connect API is requested through the customer’s DNV contact person. DNV will then configure the necessary permissions in Veracity.


After this setup is complete, the application can request access tokens from Veracity and start using the API. The latest API definitions are provided directly by DNV.

Handling personal data

Some data exposed through the API may contain personal identifiable information (PII).


To protect this information, specific access scopes are required. These scopes must be included in the access token and are configured during the initial setup by DNV.


If a request is made for personal data without the required scope, that information will either be omitted or returned as empty. This ensures compliance with data protection requirements.