1a User Roles
post
/api/v1/import/user-project-roles
This API will assign project roles for users based on the project number and email address of the record. If the deactivated parameter is set to true, the API will remove all the roles of the user for that project. The email address must match an existing user in TPM with the appropriate user permissions for that role.
Request
Header Parameters
-
Authentification(required):
The protocol for the API requires a valid username and password for TPM.
Supported Media Types
- application/json
- application/json
Root Schema : schema
Type:
Show Source
object
-
Deactivated: string
Boolean parameterExample:
False
-
EMail: string
Email address of TPMExample:
user1@company.com
-
MainJobNumber: string
Maximum Length:
300
The project/job this subcontract is written against.Example:24290012
-
ProjectRoles: string
Signer - sets the user as an invoice signer, Authorizer - sets the user as a payment authorizer, Compliance Manager - sets the user as a compliance manager, Project Manager - sets the user as a TPM Project Manager, Invoice Approver - sets the user as an invoice approverExample:
Signer
-
UserName: string
TPM user name, can be blank if unknown
Examples
Back to Top
Response
Supported Media Types
- application/json
200 Response
The job was successfully created.
Root Schema : schema
Type:
Show Source
object
-
URI: string
Endpoint for job-audit retrievalExample:
https://services.texturacorp.com/ebis/api/v1/import/user-project-roles/11
Examples
Default Response
Links to working URLs
Links
- Production URL
-
https://services.texturacorp.com/ebis/api/v1/import/user-project-roles
- Test URL
-
https://usint1.textura.oraclecloud.com/ebis/api/v1/import/user-project-roles