1b Subcontracts Audit
get
/api/v1/import/insert-contracts/{jobID}
This API allows the user to import subcontract(s), using a unique combination of the parameters: ContractNumber, VendorID, and Project. In order for subcontracts to be created, a project must exist prior to subcontract creation. If the subcontract does not exist in Texura, Textura will create a new subcontract with the specified values. If the subcontract does exist in Textura and if the subcontract has not been completed (accepted by the subcontractors), the existing subcontract will be replaced with the subcontract import data.
The successful import of a subcontract involves a structured approach that consists of two key elements: subcontract specifications and subcontract component specifications. Subcontract specifications outline the general requirements and terms associated with identifying the subcontract to be made, while subcontract component specifications provide more detailed budgetline information for the subcontract. When navigating the parameters associated with this API, it is important to recognize that the components parameter is an array that contains multiple sub-parameters. This array is allows the user to define budgetline information as well as detail unit billing information. For further clarification on the components parameter and general payload syntax, users are encouraged to review the request body section and to refer to the payload examples.
The successful import of a subcontract involves a structured approach that consists of two key elements: subcontract specifications and subcontract component specifications. Subcontract specifications outline the general requirements and terms associated with identifying the subcontract to be made, while subcontract component specifications provide more detailed budgetline information for the subcontract. When navigating the parameters associated with this API, it is important to recognize that the components parameter is an array that contains multiple sub-parameters. This array is allows the user to define budgetline information as well as detail unit billing information. For further clarification on the components parameter and general payload syntax, users are encouraged to review the request body section and to refer to the payload examples.
Request
Path Parameters
-
jobID(required): integer(int64)
Unique identifier of the job number.
Header Parameters
-
Authentification(required): string
The protocol for the API requires a valid username and password for TPM.
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
The job was successfully created.
Root Schema : schema
Type:
Show Source
object
-
formattedMessage: string
Example:
Created Subcontract #2330054.010 on Project 10-2330054
-
isoDateTime: string
Example:
2023-02-01T09:42:04.998304
-
mainJobNumber: string
Example:
01-17011
-
status: string
Example:
SUCCESS
-
subcontractNumber: string
Example:
1000
-
subJobNumber: string
Example:
17011
-
texturaJobID: number
Example:
61
-
totalDuplicate: number
Example:
0
-
totalError: number
Example:
1
-
totalInfo: number
Example:
0
-
totalSuccess: number
Example:
0
-
vendorID: string
Example:
RON095
Examples
202 Response
Accepted. Encountered when the requestor has asked for request export data or an audit log, but the request is still in process.
Default Response
Links to working URLs
Links
- Production URL
-
https://services.texturacorp.com/ebis/api/v1/import/insert-contracts/{jobID}
- Test URL
-
https://usint1.textura.oraclecloud.com/ebis/api/v1/import/insert-contracts/{jobID}