Create Bid
create_bidCreate a bid in a bid package by providing project, bid package, and vendor IDs. Set bid details such as amount, comments, and submission status.
Instructions
Create a Bid within a Bid Package. To submit a bid in Bid Management 2.0, a bid form must exist since the bid will be submitted against the bid form. Pass the record's fields as top-level arguments — they are nested under "bid" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and bid_package_id must identify an existing parent record — resolve it with the matching list tool first. Creates the bid and returns it with its new id (HTTP 201); calling it again creates another record. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, bid_package_id, vendor_id. Procore API: Preconstruction > Bid Management. Endpoint: POST /rest/v1.0/projects/{project_id}/bid_packages/{bid_package_id}/bids
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| submitted | No | JSON request body field — vendor submitted Bid | |
| vendor_id | Yes | JSON request body field — vendor responsible for bid | |
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| recipient_ids | No | JSON request body field — array of Login IDs to add as recipients | |
| bid_package_id | Yes | URL path parameter — unique identifier of the bid package | |
| bidder_comments | No | JSON request body field — comments | |
| lump_sum_amount | No | JSON request body field — lump sum (overall) amount | |
| is_bidder_committed | No | JSON request body field — bidder committed |