Prime Contracts - Procore Data Target Requirements
DataBlend supports the API calls to Create and Update Prime Contracts within Procore leveraging the Procore API.
| DataBlend Query Object (SDK) | Procore Object (API) | Required | Notes |
| project_id | project_id | Yes | Procore project the Prime Contract belongs to. Sent at the top level of the payload. The Procore company is set on the data target configuration (CompanyId), not in the query. |
| prime_contract_id | prime_contract_id | Required for Update; leave empty for Create | ID of the Prime Contract |
| primecontractattachments | attachments | Comma-separated attachment values. When present, the request is sent as multipart/form-data with each value uploaded as an attachment part. | |
| accounting_method | accounting_method | Accounting method for line items. Allowed values: amount, unit. | |
| actual_completion_date | actual_completion_date | Format: YYYY-MM-DD. |
|
| approval_letter_date | approval_letter_date | Format: YYYY-MM-DD. |
|
| architect_id | architect_id | Vendor ID of the architect. The vendor must be associated with the target project. | |
| contract_date | contract_date | Format: YYYY-MM-DD. |
|
| contract_estimated_completion_date | contract_estimated_completion_date | Format: YYYY-MM-DD. |
|
| contract_start_date | contract_start_date | Format: YYYY-MM-DD. |
|
| contractor_id | contractor_id | Vendor ID of the contractor. | |
| currency_exchange_rate | currency_exchange_rate | Decimal (e.g. 1.5). Only accepted by Procore when the multicurrency feature flag is enabled on the account. | |
| currency_iso_code | currency_iso_code | ISO 4217 currency code (e.g. USD, EUR). Only accepted by Procore when the multicurrency feature flag is enabled on the account. | |
| customfield%{custom_field_definition_id} | custom_field_%{custom_field_definition_id} | Custom field value. Replace %{custom_field_definition_id} with the custom field definition ID. The value must match the data type of the custom field definition. | |
| description | description | Description of the Prime Contract. Free text. | |
| drawing_revision_ids | drawing_revision_ids | Pipe-separated integer IDs (e.g. 1|2|3) of drawing revisions to attach. |
|
| exclusions | exclusions | Contract exclusions. Free text. | |
| executed | executed | Boolean. Indicates whether the contract has been executed. | |
| execution_date | execution_date | Format: YYYY-MM-DD. |
|
| file_version_ids | file_version_ids | Pipe-separated integer IDs (e.g. 1|2|3) of file versions to attach. |
|
| form_ids | form_ids | Pipe-separated integer IDs (e.g. 1|2|3) of forms to attach. |
|
| image_ids | image_ids | Pipe-separated integer IDs (e.g. 1|2|3) of images to attach. |
|
| inclusions | inclusions | Contract inclusions. Free text. | |
| issued_on_date | issued_on_date | Format: YYYY-MM-DD. |
|
| letter_of_intent_date | letter_of_intent_date | Format: YYYY-MM-DD. |
|
| number | number | Prime Contract number. Free text. | |
| origin_data | origin_data | Third-party data reference. Free text. | |
| origin_id | origin_id | Third-party ID reference. Free text. | |
| retainage_percent | retainage_percent | Numeric value (e.g. 10 for 10%). | |
| returned_date | returned_date | Format: YYYY-MM-DD. |
|
| signed_contract_received_date | signed_contract_received_date | Format: YYYY-MM-DD. |
|
| status | status | Allowed values: Draft, Out For Bid, Out For Signature, Approved, Complete, Terminated. |
|
| title | title | Title of the Prime Contract. Free text. | |
| upload_ids | upload_ids | Pipe-separated upload IDs (e.g. a|b|c) of uploads to attach. |
|
| vendor_id | vendor_id | Vendor ID. |
More questions about Procore API requirements? Please visit Prime Contracts.