POST /rest/v1.0/rfqs

Create a new RFQ in a specified Project and Contract.

Servers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"
`Procore-Company-Id`	Integer	Yes	Unique company identifier associated with the Procore User Account.

Name	Type	Required	Description
`project_id`	Integer	Yes	Unique identifier for the project.
`contract_id`	Integer	Yes	Contract ID
`rfq`	Object	Yes
`rfq.specification_section_id`	Integer	No	Specification Section ID
`rfq.prostore_file_ids[]`	Array	No	Prostore File IDs
`rfq.description`	String	No	Description
`rfq.spec_section_description`	String	No	Specification Section description
`rfq.number`	String	No	Number
`rfq.original_quote`	Number	No	Original quote
`rfq.status`	String	No	Status Possible values: `"under_review"` `"pending_final_approval"` `"closed"` `"revise_and_resubmit"` `"out_for_pricing"` `"withdrawn"`
`rfq.spec_section_number`	String	No	Specification Section number
`rfq.location_id`	Integer	No	Location ID
`rfq.assigned_id`	Integer	No	Assigned ID
`rfq.estimated_status`	String	No	Estimated status Possible values: `"rom"` `"final"`
`rfq.estimated_schedule_impact`	Integer	No	Estimated schedule impact in days
`rfq.private`	Boolean	No	If true, visible to admins only; otherwise visible to those with access to the parent contract. Default value: false
`rfq.title`	String	Yes	Title
`rfq.estimated_amount`	Number	No	Estimated amount
`rfq.change_event_event_id`	Integer	No	Change Event ID
`rfq.cost_code_id`	Integer	No	Cost Code ID
`rfq.due_date`	String	No	Due date

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.