GET /rest/v1.0/rfqs

Return a list of all RFQs in a specified Project and Contract.

See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint.

Servers

Request headers

Name Type Required Description
Procore-Company-Id Integer Yes

Unique company identifier associated with the Procore User Account.

Query parameters

Name Type Required Description
page Integer No

Page

filters[commitment_contract_id] Integer No

Return item(s) with the specified Commitment Contract ID.

project_id Integer Yes

Unique identifier for the project.

contract_id Integer Yes

Contract ID

per_page Integer No

Elements per page

filters[created_at] String No

Return item(s) created within the specified ISO 8601 datetime range. Formats: YYYY-MM-DD...YYYY-MM-DD - Date YYYY-MM-DDTHH:MM:SSZ...YYYY-MM-DDTHH:MM:SSZ - DateTime with UTC Offset YYYY-MM-DDTHH:MM:SS+XX:00...YYYY-MM-DDTHH:MM:SS+XX:00` - Datetime with Custom Offset

filters[updated_at] String No

Return item(s) last updated within the specified ISO 8601 datetime range. Formats: YYYY-MM-DD...YYYY-MM-DD - Date YYYY-MM-DDTHH:MM:SSZ...YYYY-MM-DDTHH:MM:SSZ - DateTime with UTC Offset YYYY-MM-DDTHH:MM:SS+XX:00...YYYY-MM-DDTHH:MM:SS+XX:00 - Datetime with Custom Offset

filters[status] String No

Returns item(s) with the specified value for RFQ status.

Possible values:

  • "under_review"
  • "pending_final_approval"
  • "closed"
  • "revise_and_resubmit"
  • "out_for_pricing"
  • "withdrawn"

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. 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.
  3. Click Test request to test run your request to the API and see the API's response.