Developer Feedback for Procore Connect API and Developer Portal

Welcome to the Procore Developer Feedback Forum specifically focused on the Procore Connect API and Developer Portal (developers.procore.com).

We’d like to hear any ideas you have for how we can improve the Procore Connect Developer Experience. Please use this forum to provide feedback and suggest enhancements. You can also vote and comment on other ideas suggested by other Procore developers.

This forum is actively monitored by Procore’s Product Management Team.

How can we improve Procore's Developer Experience?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Access the PDF exports of Procore resources through the REST API

    We have been able to use the APIs to access data for different resources (RFIs, Observation Items, Submittals etc.) but couldn’t find a way to get URLs for the PDF exports of these resources. Please include a url field for PDF resource in the JSON response similar to the attachments URL so that we can access the PDF exports of Procore resources through the REST API?

    2 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. TimeStamp Workflow Steps

    In the API Documentation, please expose timestamps for when a tool moves to the next workflow step. This would be super helpful for tracking accurate durations and highlighting problem areas, specifically for tools like RFI, Submittal, and Punch.

    2 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  3. Expose the `corporate_office` field in the API

    This field shows in the UI, but not the API

    1 vote
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  4. Timezones carrying over on Project Templates

    "Just got a ticket from one of my teams on the west coast. They asked us to update the time zone of their project. I noticed our template was set to east coast time. But that made me do a few tests to confirm the time zone carried forward. Unfortunately, it doesn't appear that it carries to the new project. It also doesn't appear there is a way to set this via the APIs. "

    1 vote
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Bulk List Project Dates, Budget, Schedule and others

    We have more than 700 projects at any given time within our company. While building custom integration with our warehouse, I noticed that there is currently no ability to download bulk data about Dates, Budget and Schedule at company level. It would be great if we can have an api end point that could pull bulk data at company level. Currently, I will be coding to run a loop to pull each project details one at a time and then bind them which is time and resource consuming.

    5 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  6. ProjectUser Identification

    For us to display who is working on a Project, we pull information from ProjectUser - excellent.
    However, we have 18 individuals who are by default added to each project (IT Support, Health & Safety, Environmental, O&M Coordinators, Board etc...). They are incl on each Project and we want to exclude them from the reporting on each Project for some aspects.
    We can manually identify these users via the ID's however it would be more appropriate to exclude based on settings incl:
    a) In our template project, eight individuals are listed yet these are not returned in ProjectUser as attached…

    1 vote
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add the ability to set submittal approvers via API

    The submittal creation and update API does not allow setting the approvers for the submittal. This limits our ability to fully automate the creation of submittals.

    3 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  8. I want use Impement procore connect rest api in sharepoint add-ins

    I am working in procore connect rest api in sharepoint add-ins

    1 vote
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add custom fields

    Unable to POST to custom fields with inability to create custom fields is a blocking item. Why doesn't Procore allow custom user fields and API calls to support it's data feed?

    10 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  10. Update Budget Forecast via Update Budget Line Item Endpoint

    Allow updating the forecast amount (budget_forecast) since this is commonly updated manually. Will provide support/experience that it used in the UI.

    1 vote
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add additional fields to List Observation API call

    Add in additional fields to the List Observation API call (https://developers.procore.com/reference/observations#list-observation-types) including the "distribution_members", "contributing_behavior", "contributing_condition", and "hazard" related fields.

    This will help reduce API traffic of having to use the Show call for each observation.

    3 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add "Ball in Court" Date from the Submittals Workflow to API Integration

    When a submittal is created we have the ability to create a responsibility workflow with associated responsible contractors/personnel. Each of these members have a "Ball in Court Due Date" that lead up to the "Final Due Date". If we had this "Ball in Court Due Date" as an API integration, we would be able to track each submittal through it's life cycle to ensure each task within it was being done in time.

    6 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add additional fields to List Meetings API

    Add fields found in Show Meeting API call plus the created_at, updated_at, and user creator info to the List Meetings API: https://developers.procore.com/reference/meetings#list-meetings

    This will enable reduced API traffic of having to iterate each meeting to get the details. A search option on updated_at would also be useful.

    2 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  14. Provide direct cost line item records in direct cost API call

    Add the direct cost line item details (https://developers.procore.com/reference/direct-costs#list-direct-cost-line-items) into the direct cost list call: https://developers.procore.com/reference/direct-costs#list-direct-cost-items

    This would save a lot of additional API traffic required to get the line item detail.

    2 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add Document Permissions to API

    Currently in the Procore Documents UI, a user can "lock" a file or folder and add explicit permissions to users. This is not available through the API which means if a file/folder is created through the API then it has to be given "explicit_permissions" which means only the user or admins have access, or everyone with documents can access it.

    2 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add Signed Change Order Received Date to API on CO Packages

    Signed Change order Received Date is a field on screen of a change order package, but it is not returned by the API.

    2 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add origin_id and _data to timecard entries

    Please look at adding origin_id and origin_data to timecard entry objects. And allow filter[origin_id] searching.
    It would make external integration so much more reliable. Presently, updating a timecard requires a full download of cards for a time period and filtering down to find unique project/person/code/date to adjust hours. If any other item changed (say they clicked on wrong code or person, its almost impossible to find. Also, if timecard is deleted during reconciliation process, that card is impossible to find.
    Only solution we have at present is to delete all time cards for a given period and re-create them all.

    2 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Flag idea as inappropriate…  ·  Admin →
  18. Remove a user from a project via API

    Allow removing a user from a project directory via the API.

    The need to remove a user from a project has already been identified by many systems including Procore - the feature exists on Procore's web UI.

    Adding this feature to the API would allow integrations to meet this requirement and maintain data integrity in disparate systems in an automated fashion.

    9 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Limited Release  ·  1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  19. Custom tools

    Add API support for custom tools

    9 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  20. Product Roadmap/Timeline for API Enhancements and Development

    We would be interested in knowing the direction API development is headed, which enhancements are priorities, and estimates of when specific new features will be available to us.

    11 votes
    Sign in Sign in with Procore
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Developer Feedback for Procore Connect API and Developer Portal

Feedback and Knowledge Base