List every Procore API category with its modules and endpoint counts. Use this as the first step when exploring what Procore can do — it returns a hierarchical map (Category > Module > endpoint count) that scopes any follow-up discovery or search call. Returns a JSON object; takes no inputs.

List every Procore endpoint within a specific category (and optional module). Use after procore_discover_categories to drill into a focused area such as RFIs, Submittals, or Budgets. Filter further by free-text summary or HTTP method. Returns a JSON array of endpoint metadata (operationId, summary, method, path).

Fetch the full parameter schema, request body shape, and response format for a single Procore endpoint. Pass an operation_id from procore_discover_endpoints. Use this right before calling procore_api_call so you know exactly which path/query/body parameters to provide. Returns a JSON object.

Execute any Procore REST API call. This is the workhorse — first use the discover/search tools to find the right endpoint, then call it here. Handles OAuth automatically (uses the saved tokens), substitutes path placeholders, encodes nested query brackets (__ becomes [/]), and returns the parsed JSON response with pagination + rate-limit metadata.

Full-text search across every Procore API endpoint summary, tag, and path. Use to quickly locate the right endpoint when you know roughly what you're looking for — e.g. 'RFI', 'budget', 'punch list', 'submittal'. Returns a JSON array of matches ranked by relevance.

Show the current MCP server configuration: OAuth/auth status, default company_id, the active runtime project_id, and other persisted settings. Use this to debug context issues or before switching projects. Takes no inputs.

Set a runtime configuration key (e.g. company_id or project_id) for the current session. The change persists until the server restarts. Use this to switch the default company/project context without restarting the MCP server. Returns a confirmation message.

Returns a list of workflowable tools for a given company. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/tools

Returns a list of all workflow templates for a given company. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/templates

Returns the details of a specific workflow template version. Use this to fetch the full details of a specific Workflows by its identifier. Returns a JSON object describing the requested Workflows. Required parameters: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/templates/versions/{id}

List Workflow Presets (Project). Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, filters[tool_type]. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/presets

List Workflow Presets (Company). Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, filters[tool_type]. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/presets

Get details of a specific workflow preset. Use this to fetch the full details of a specific Workflows by its identifier. Returns a JSON object describing the requested Workflows. Required parameters: company_id, project_id, id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/presets/{id}

Updates a workflow preset for a project tool. Use this to update an existing Workflows (only the supplied fields are changed). Updates the specified Workflows and returns the modified object on success. Required parameters: company_id, project_id, id. Procore API (v2.0): Core > Workflows. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/presets/{id}

Get details of a specific workflow preset. Use this to fetch the full details of a specific Workflows by its identifier. Returns a JSON object describing the requested Workflows. Required parameters: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/presets/{id}

Updates a workflow preset for a company tool. Use this to update an existing Workflows (only the supplied fields are changed). Updates the specified Workflows and returns the modified object on success. Required parameters: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: PATCH /rest/v2.0/companies/{company_id}/workflows/presets/{id}

Updates assignees and workflow manager for a workflow preset for a project tool. Use this to update an existing Workflows (only the supplied fields are changed). Updates the specified Workflows and returns the modified object on success. Required parameters: company_id, project_id, id. Procore API (v2.0): Core > Workflows. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/presets/{id}/assignees

Updates assignees and workflow manager for a workflow preset for a company tool. Use this to update an existing Workflows (only the supplied fields are changed). Updates the specified Workflows and returns the modified object on success. Required parameters: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: PATCH /rest/v2.0/companies/{company_id}/workflows/presets/{id}/assignees

Returns a list of all workflows possible assignees for a given project and tool. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, tool_type. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/possible_assignees

Returns a list of all workflows possible assignees for a given company and tool. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, tool_type. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/possible_assignees

Returns a list of all workflow managers for a given project and tool. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, tool_type. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/workflow_managers

Returns a list of all workflow managers for a given company and tool. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, tool_type. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/workflow_managers

Returns a list of workflow instances for a given project. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, filters[tool_type]. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances

Creates a new workflow instance for a given project. The template_id and preset_id options can be used to specify a specific template. If neither are specified, the default preset will be used. If both are specified, the preset_id will be used. Use this to create a new Workflows in Procore. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, tool_type, item_id. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances

Returns a list of workflow instances for a given company. Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, filters[tool_type]. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/instances

Creates a new workflow instance for a given company. The template_id and preset_id options can be used to specify a specific template. If neither are specified, the default preset will be used. If both are specified, the preset_id will be used. Use this to create a new Workflows in Procore. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, tool_type, tool_subtype, item_id. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/workflows/instances

Returns a single instance for a given project. Use this to fetch the full details of a specific Workflows by its identifier. Returns a JSON object describing the requested Workflows. Required parameters: company_id, project_id, id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances/{id}

Returns a single workflow instance for a given company. Use this to fetch the full details of a specific Workflows by its identifier. Returns a JSON object describing the requested Workflows. Required parameters: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/instances/{id}

Respond to a Workflow Instance (Project). Use this to perform the respond to action on Workflows. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: project_id, company_id, id, current_step_occurrence_id, selected_response_option_id, attachments. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances/{id}/responses

Respond to a Workflow Instance (Company). Use this to perform the respond to action on Workflows. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, id, current_step_occurrence_id, selected_response_option_id, attachments. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/workflows/instances/{id}/responses

Returns an ordered list of history events for a given project workflow instance. Each event in the history array has a type field and a details object. The following event types are supported: WorkflowStarted — emitted when the workflow begins. json { "type": "WorkflowStarted", "details": { "started_at": "2024-01-15T10:00:00Z" } } WorkflowTerminated — emitted when the workflow is terminated before completion. ```json { "type": "WorkflowTerminated", "detai... Use this to fetch the full details of a specific Workflows by its identifier. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances/{id}/history

Returns an ordered list of history events for a given company workflow instance. Each event in the history array has a type field and a details object. The following event types are supported: WorkflowStarted — emitted when the workflow begins. json { "type": "WorkflowStarted", "details": { "started_at": "2024-01-15T10:00:00Z" } } WorkflowTerminated — emitted when the workflow is terminated before completion. ```json { "type": "WorkflowTerminated", "detai... Use this to fetch the full details of a specific Workflows by its identifier. Returns a paginated JSON array of Workflows. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: GET /rest/v2.0/companies/{company_id}/workflows/instances/{id}/history

Adds additional assignees to a step occurrence on a project workflow instance. Use this to create a new Workflows in Procore. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, id, step_occurrence_id, required, reason, assignee_ids. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances/{id}/additional_assignees

Adds additional assignees to a step occurrence on a company workflow instance. Use this to create a new Workflows in Procore. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, id, step_occurrence_id, required, reason, assignee_ids. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/workflows/instances/{id}/additional_assignees

Terminates the current instance and restarts a new instance from the beginning. Returns the new instance information. Use this to perform the restart a action on Workflows. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, id. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances/{id}/restart

Terminates the current instance and restarts a new instance from the beginning. Returns the new instance information. Use this to perform the restart a action on Workflows. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/workflows/instances/{id}/restart

Terminate a Workflow Instance (Project) (Public). Use this to perform the terminate a action on Workflows. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, id. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances/{id}/terminate

Terminate a Workflow Instance (Company) (Public). Use this to perform the terminate a action on Workflows. Creates a new Workflows and returns the created object on success (HTTP 201). Required parameters: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/workflows/instances/{id}/terminate

Asynchronously bulk create workflow instances for a list of project-level items. If an active instance already exists for an item, a failure will be returned for that item. The returned async operation id can be used to query for status using the GET /rest/v2.0/companies/{company_id}/async_operations/{operation_id} API. The result field of the operation contains a list of completed and failed i... Use this to create many Workflows records in a single request. Creates many Workflows records in one request and returns the created collection (HTTP 201). Partial failures may occur — check each item's status. Required parameters: company_id, project_id, tool_type, items. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/workflows/instances/bulk_create

Asynchronously bulk create workflow instances for a list of company-level items. If an active instance already exists for an item, a failure will be returned for that item. The returned async operation id can be used to query for status using the GET /rest/v2.0/companies/{company_id}/async_operations/{operation_id} API. The result field of the operation contains a list of completed and failed i... Use this to create many Workflows records in a single request. Creates many Workflows records in one request and returns the created collection (HTTP 201). Partial failures may occur — check each item's status. Required parameters: company_id, tool_type, items. Procore API (v2.0): Core > Workflows. Endpoint: POST /rest/v2.0/companies/{company_id}/workflows/instances/bulk_create

Returns a List of webhooks resources for the company. Use this to enumerate Webhooks when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Webhooks. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, payload_version. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: GET /rest/v2.0/companies/{company_id}/webhooks/resources

Returns a List of webhooks resources for the project. Use this to enumerate Webhooks when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Webhooks. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, payload_version. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/webhooks/resources

Returns Configuration Data for Uom Master List. Use this to fetch the full details of a specific Units of Measure records by its identifier. Returns a paginated JSON array of Units of Measure records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API (v2.0): Construction Financials > Units of Measure. Endpoint: GET /rest/v2.0/companies/{company_id}/uoms/configuration

Returns an array of Triggers for the company webhook. Use this to enumerate Webhooks when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Webhooks. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, hook_id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: GET /rest/v2.0/companies/{company_id}/webhooks/hooks/{hook_id}/triggers

Create Triggers for the Company Webhook. Use this to create a new Webhooks in Procore. Creates a new Webhooks and returns the created object on success (HTTP 201). Required parameters: company_id, hook_id, resource_name, event_type. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: POST /rest/v2.0/companies/{company_id}/webhooks/hooks/{hook_id}/triggers

Returns an array of Triggers for the project webhook. Use this to enumerate Webhooks when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Webhooks. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, hook_id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/webhooks/hooks/{hook_id}/triggers

Create Triggers for the Project Webhook. Use this to create a new Webhooks in Procore. Creates a new Webhooks and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, hook_id, resource_name, event_type. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/webhooks/hooks/{hook_id}/triggers

Delete Company Webhooks Trigger. Use this to permanently delete the specified Webhooks. This cannot be undone. Permanently removes the specified Webhooks. This action cannot be undone. Required parameters: company_id, hook_id, id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: DELETE /rest/v2.0/companies/{company_id}/webhooks/hooks/{hook_id}/triggers/{id}

Delete Project Webhooks Trigger. Use this to permanently delete the specified Webhooks. This cannot be undone. Permanently removes the specified Webhooks. This action cannot be undone. Required parameters: company_id, project_id, hook_id, id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/webhooks/hooks/{hook_id}/triggers/{id}

Create multiple Triggers for the Company Webhook in a single request. Use this to create many Webhooks records in a single request. Creates many Webhooks records in one request and returns the created collection (HTTP 201). Partial failures may occur — check each item's status. Required parameters: company_id, hook_id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: POST /rest/v2.0/companies/{company_id}/webhooks/hooks/{hook_id}/triggers/bulk

Deletes multiple Triggers for the Company Webhook in a single request. Use this to permanently delete the specified Webhooks. This cannot be undone. Permanently removes the specified Webhooks. This action cannot be undone. Required parameters: company_id, hook_id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: DELETE /rest/v2.0/companies/{company_id}/webhooks/hooks/{hook_id}/triggers/bulk

Create multiple Triggers for the Project Webhook in a single request. Use this to create many Webhooks records in a single request. Creates many Webhooks records in one request and returns the created collection (HTTP 201). Partial failures may occur — check each item's status. Required parameters: company_id, project_id, hook_id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/webhooks/hooks/{hook_id}/triggers/bulk

Deletes multiple Triggers for the Project Webhook in a single request. Use this to permanently delete the specified Webhooks. This cannot be undone. Permanently removes the specified Webhooks. This action cannot be undone. Required parameters: company_id, project_id, hook_id. Procore API (v2.0): Platform - Developer Tools > Webhooks. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/webhooks/hooks/{hook_id}/triggers/bulk

Returns options for distribution members that the current user can add to Task Items. Use this to enumerate Tasks when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Tasks. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.0): Core > Tasks. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/task_items_project_distribution_members/options

Returns default distribution members for Task Items for the given project. Use this to enumerate Tasks when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Tasks. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.0): Core > Tasks. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/task_items_project_distribution_members/default

Fetches active support pin for given company. Use this to fetch the full details of a specific Company Settings by its identifier. Returns a paginated JSON array of Company Settings. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API (v2.0): Company Admin > Company Settings. Endpoint: GET /rest/v2.0/companies/{company_id}/support_pins

Creates a support pin for the given company. Use this to create a new Company Settings in Procore. Creates a new Company Settings and returns the created object on success (HTTP 201). Required parameters: company_id. Procore API (v2.0): Company Admin > Company Settings. Endpoint: POST /rest/v2.0/companies/{company_id}/support_pins

Return a list of all Submittals. Use this to read information about Submittals from Procore. Returns a paginated JSON array of Submittals. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Submittals. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/submittals

Returns all specification settings in a specified Project. Use this to enumerate Specifications when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Specifications. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, specification_configuration. Procore API (v2.1): Project Management > Specifications. Endpoint: GET /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_configuration

Save changes in configurations and Returns all updated specification settings in a specified Project. Use this to update an existing Specifications (only the supplied fields are changed). Updates the specified Specifications and returns the modified object on success. Required parameters: company_id, project_id, specification_configuration. Procore API (v2.1): Project Management > Specifications. Endpoint: PATCH /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_configuration

This endpoint returns a paginated list potential distribution members for specifications. Use this to enumerate Specifications when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Specifications. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.1): Project Management > Specifications. Endpoint: GET /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_configuration/potential_distribution_members

This endpoint returns a paginated list distribution groups with users for specifications. Use this to enumerate Specifications when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Specifications. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.1): Project Management > Specifications. Endpoint: GET /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_configuration/distribution_groups

This endpoint returns a paginated list of Specification Areas for a Project. Use this to enumerate Specifications when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Specifications. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.1): Project Management > Specifications. Endpoint: GET /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_areas

Creates a new Specification Area in the specified Project. Use this to create a new Specifications in Procore. Creates a new Specifications and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, name. Procore API (v2.1): Project Management > Specifications. Endpoint: POST /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_areas

Updates an existing Specification Area in the specified Project. Use this to update an existing Specifications (only the supplied fields are changed). Updates the specified Specifications and returns the modified object on success. Required parameters: company_id, project_id, specification_area_id. Procore API (v2.1): Project Management > Specifications. Endpoint: PUT /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_areas/{specification_area_id}

Delete an existing Specification Area in the specified Project. Use this to permanently delete the specified Specifications. This cannot be undone. Permanently removes the specified Specifications. This action cannot be undone. Required parameters: company_id, project_id, specification_area_id. Procore API (v2.1): Project Management > Specifications. Endpoint: DELETE /rest/v2.1/companies/{company_id}/projects/{project_id}/specification_areas/{specification_area_id}

Return a list of roles for a company. Use this to enumerate Company Settings when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Company Settings. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API (v2.0): Company Admin > Company Settings. Endpoint: GET /rest/v2.0/companies/{company_id}/roles

POST Company Role. Use this to perform the post company action on Company Settings. Creates a new Company Settings and returns the created object on success (HTTP 201). Required parameters: company_id. Procore API (v2.0): Company Admin > Company Settings. Endpoint: POST /rest/v2.0/companies/{company_id}/roles

PATCH Company Role. Use this to update an existing Company Settings (only the supplied fields are changed). Updates the specified Company Settings and returns the modified object on success. Required parameters: company_id, id. Procore API (v2.0): Company Admin > Company Settings. Endpoint: PATCH /rest/v2.0/companies/{company_id}/roles/{id}

DELETE Company Role. Use this to permanently delete the specified Company Settings. This cannot be undone. Permanently removes the specified Company Settings. This action cannot be undone. Required parameters: company_id, id. Procore API (v2.0): Company Admin > Company Settings. Endpoint: DELETE /rest/v2.0/companies/{company_id}/roles/{id}

Reorder Company Role. Use this to perform the reorder company action on Company Settings. Creates a new Company Settings and returns the created object on success (HTTP 201). Required parameters: company_id, order. Procore API (v2.0): Company Admin > Company Settings. Endpoint: POST /rest/v2.0/companies/{company_id}/roles/reorder

Update the Due Date for a Requisition (Subcontractor Invoice). Use this to update an existing Commitments (only the supplied fields are changed). Updates the specified Commitments and returns the modified object on success. Required parameters: company_id, project_id, id. Procore API (v2.0): Construction Financials > Commitments. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/requisitions/{id}/payment_details

Lists the requisition compliance documents Procore Pay must be enabled to use this endpoint.. Use this to enumerate Payments when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Payments. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, invoice_id. Procore API (v2.0): Construction Financials > Payments. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/compliance/invoices/{invoice_id}/documents

Creates a compliance document Procore Pay must be enabled to use this endpoint.. Use this to create a new Payments in Procore. Creates a new Payments and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, invoice_id. Procore API (v2.0): Construction Financials > Payments. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/compliance/invoices/{invoice_id}/documents

Gets the requisition compliance document Procore Pay must be enabled to use this endpoint.. Use this to fetch the full details of a specific Payments by its identifier. Returns a JSON object describing the requested Payments. Required parameters: company_id, project_id, invoice_id, document_id. Procore API (v2.0): Construction Financials > Payments. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/compliance/invoices/{invoice_id}/documents/{document_id}

Updates the requisition compliance document Procore Pay must be enabled to use this endpoint.. Use this to update an existing Payments (only the supplied fields are changed). Updates the specified Payments and returns the modified object on success. Required parameters: company_id, project_id, invoice_id, document_id. Procore API (v2.0): Construction Financials > Payments. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/compliance/invoices/{invoice_id}/documents/{document_id}

Deletes the requisition compliance document Procore Pay must be enabled to use this endpoint.. Use this to permanently delete the specified Payments. This cannot be undone. Permanently removes the specified Payments. This action cannot be undone. Required parameters: company_id, project_id, invoice_id, document_id. Procore API (v2.0): Construction Financials > Payments. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/compliance/invoices/{invoice_id}/documents/{document_id}

Lists the requisition compliance attachments Procore Pay must be enabled to use this endpoint.. Use this to enumerate Payments when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Payments. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, invoice_id. Procore API (v2.0): Construction Financials > Payments. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/compliance/invoices/{invoice_id}/documents/attachments

Returns users assigned to punch items with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/assignees

Returns vendor companies of punch item assignees with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/assignee_companies

Returns users who currently have ball in court on punch items with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/ball_in_court

Returns users who have closed punch items with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/closed_by_contacts

Returns users who have created punch items with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/creators

Returns users assigned as final approvers on punch items with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/final_approvers

Returns users assigned as punch item managers with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/punch_item_managers

Returns trades associated with punch items with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/trades

Returns punch item types with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/types

Returns locations associated with punch items with pagination and optional search. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Punch List records. Required parameters: company_id, project_id. Procore API (v2.0): Project Management > Punch List. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/punch_list/locations

Bulk Remove Project Memberships for many parties on the given Project. Currently, the maximum number of party IDs that can be processed in a single request is 1000. If more than 1000 party IDs are provided, only the first 1000 will be processed. This endpoint can currently only be used to remove reference users from a project. It cannot be used to remove a user who has a login or to remove vendors. Use this to permanently delete the specified Directory records. This cannot be undone. Permanently removes the specified Directory records. This action cannot be undone. Required parameters: company_id, project_id, party_ids. Procore API (v2.0): Core > Directory. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/project_memberships/bulk_remove

Show the specified Project Inspection Template Item Evidence Configuration. Use this to fetch the full details of a specific Inspections by its identifier. Returns a paginated JSON array of Inspections. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, template_item_id. Procore API (v2.0): Project Management > Inspections. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/inspection_template_items/{template_item_id}/evidence_configuration

Updates the specified Project Inspection Template Item Evidence Configuration. Use this to update an existing Inspections (only the supplied fields are changed). Updates the specified Inspections and returns the modified object on success. Required parameters: company_id, project_id, template_item_id. Procore API (v2.0): Project Management > Inspections. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/inspection_template_items/{template_item_id}/evidence_configuration

List project dates associated with a project. Use this to enumerate Project records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Project records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.0): Core > Project. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/project_dates

Returns a list of Prime Contracts for a given project. Use this to enumerate Prime Contracts when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Prime Contracts. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts

Creates a new Prime Contract for a given project. Use this to create a new Prime Contracts in Procore. Creates a new Prime Contracts and returns the created object on success (HTTP 201). Required parameters: company_id, project_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts

Returns a Prime Contract for a given project. Use this to fetch the full details of a specific Prime Contracts by its identifier. Returns a JSON object describing the requested Prime Contracts. Required parameters: company_id, project_id, prime_contract_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{prime_contract_id}

Updates a Prime Contract for a given project. Use this to update an existing Prime Contracts (only the supplied fields are changed). Updates the specified Prime Contracts and returns the modified object on success. Required parameters: company_id, project_id, prime_contract_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{prime_contract_id}

Deletes a Prime Contract for a given project. Use this to permanently delete the specified Prime Contracts. This cannot be undone. Permanently removes the specified Prime Contracts. This action cannot be undone. Required parameters: company_id, project_id, prime_contract_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{prime_contract_id}

Check the status of a PDF document generation for a prime contract. Note: This endpoint is currently only supported in Procore Zones US01 && US02. Use this to retrieve a downloadable file or export URL for Prime Contracts. Returns a JSON object with the file contents or download URL for Prime Contracts. Required parameters: company_id, project_id, prime_contract_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{prime_contract_id}/pdf

Creates a PDF export for a given Prime Contract. Note: This endpoint is currently only supported in Procore Zones US01 && US02. Use this to create a new Prime Contracts in Procore. Generates the export and returns a download URL or async job handle. Required parameters: company_id, project_id, prime_contract_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{prime_contract_id}/pdf

Returns a combined summary of change order and invoicing information for a specific prime contract. summary endpoints. Use this to fetch the full details of a specific Prime Contracts by its identifier. Returns a paginated JSON array of Prime Contracts. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, contract_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{contract_id}/summary