Pricing Templates

GET /rest/v1.0/workforce-planning/v2/companies/{company_id}/projects/{project_id}/resource-requests

Retrieves all Resource Requests for a specified Project within a company. This is a pageable endpoint.

Servers

https://api.procore.com

Path parameters

Name Type Required Description

Name	Type	Required	Description
`project_id`	Integer	Yes	Unique identifier for the project
`company_id`		Yes	Unique identifier for the company. This parameter accepts both formats: Recommended: Procore company ID (integer) - Use this for new integrations Legacy: LaborChart UUID format (uuid string) - Supported for backward compatibility A proxy layer automatically handles both formats, but using the Procore company ID is preferred for consistency with other Procore APIs.

project_id

Integer

Yes

Unique identifier for the project

company_id

Yes

Unique identifier for the company. This parameter accepts both formats:

Recommended: Procore company ID (integer) - Use this for new integrations
Legacy: LaborChart UUID format (uuid string) - Supported for backward compatibility

A proxy layer automatically handles both formats, but using the Procore company ID is preferred for consistency with other Procore APIs.

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

Name	Type	Required	Description
`page`	Integer	No	This is a 0-based index representing the page slice of the data you want to retrieve. Each page contains up to 400 items. 📌 Pageable Endpoints People endpoints that return multiple records support pagination. It is recommended to use this feature to prevent network timeouts from excessively large data requests. 📌 Response Structure A successful response will include the following properties: `possible_pages` (integer) → Total number of pages available to retrieve all data. - `current_page` (integer) → The 0-based index of the page retrieved. - `data` (array) → List of records returned for the requested page (up to 400 items per page). If a page value exceeds `possible_pages`, the `data` property will return an empty array.

page

Integer

No

This is a 0-based index representing the page slice of the data you want to retrieve. Each page contains up to 400 items.

📌 Pageable Endpoints People endpoints that return multiple records support pagination. It is recommended to use this feature to prevent network timeouts from excessively large data requests.

📌 Response Structure A successful response will include the following properties:

possible_pages (integer) → Total number of pages available to retrieve all data. - current_page (integer) → The 0-based index of the page retrieved. - data (array) → List of records returned for the requested page (up to 400 items per page). If a page value exceeds possible_pages, the data property will return an empty array.

How to start integrating

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.

All third party trademarks (including logos and icons) are the property of their respective owners, which do not sponsor, authorize, or endorse this website.

Pricing Templates Integrations Blog Contact Us Help

Terms of Service Privacy Policy