Skip to main content

Authentication

To use these APIs, you must authenticate using OAuth 2.0 tokens.

OAuth 2.0 Bearer access tokens are issued on behalf your application to access protected application resources.

See here to know how to obtain an Oauth2 token (access and refresh token)

OAuth2 bearer access token (sent in a header)​

Example:

curl -H "Authorization: Bearer OAUTH-ACCESS-TOKEN" https://demo.q12-tmt.com

Project permission​

User's roles and access rights change accordingly depending on the project you are working on. You must provide the headers project-id and subproject-id along with your request when accessing the project resource.

  • Project-Id: id of the project. This might be empty when you are working with tenant resource only Example: Project-id:P_1
  • Subproject-Id: id of the sub project. This might be empty when you are working with parent project only. Example: Subproject-id: SP_2
tip

Aside from the project id, you can also use the document reference of the Project document.

The headers are also accepted:

  • Project-id: Project-dm/98938
  • Subproject-id: Project-dm/98942

Reference of the target project (sub project) can be found by reading from "DocRef" field of Load project with version operation's response.