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.

  1. Batch update submittals via API

    Using the API, we can only update one submittal at a time. We had a project with 450 submittals where we updated due dates. User reported it took about 10 minutes. Sure would be nice to have a batch update feature!

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add Etag support to API

    It would be very helpful if each API endpoint could guarantee that HTTP header etags worked. The do appear to work on many endpoints, but afaik are not QA tested and therefore guaranteed to be correct.

    https://en.wikipedia.org/wiki/HTTP_ETag

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add Region field to API

    We have a need to have a field for Facility Name that cannot go into another field that is currently used (like office). We would like to use the Region field for this but it is not in the API fields. Please add.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add ability to create service hooks via the API

    For apps that need service hooks (e.g. to process webhooks), it would be nice to be able to create and configure these via the API to save the user having to create them manually and cut and paste the details. It would also mean that the app could optionally manage the rotation of service hook credentials. Key benefit is that it would make setup simpler for the user.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Be able to have multiple webhooks per namespace

    Currently it is only possible to set up one webhook for a given namespace.

    It would be unusual, but it is conceivable that a user might want to set up two (or more) instances of an integration on a single Procore company - perhaps where the Procore owner is working with different contractors, each with their own instance of the same integration (and thus each with different webhook urls).

    It is much more likely to happen in testing where multiple developers are all testing off of one sandbox.

    This can be worked around by customising the namespace for each integration…

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support more than 2 decimal place limits on API

    Client works with another party who integrates with Primavera. Their accounting system has a 5 decimal place limit and this is causing an issue when the Procore client submits a Payment Application.

    You can see this when exporting a pay app to PDF. On page 2 the fall right-hand column marked "Retainage" only has 2 decimal points. Because Primavera has 5 their system is rounding up the pay apps and this is causing a discrepancy which is causing pay apps to be rejected.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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?

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  12. We are not able to create/ update the Change Event Line Vendor & Contract details using the API.

    Create or update change event Lines through API will not 100% like application functionality. Through API we cannot pass contract id or vendor id. Here is the json format from API for change event line. It is good to have functionality.

    "change_event_line_items_attributes":[
    {
    "id":592648,
    "description":"Add caulk to bathtub base",
    "estimated_cost_amount":17705,
    "line_item_type_id":657393,
    "cost_code_id":32940
    }
    ]

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Submittal numbers returned by the API are not useful

    When reading the list of submittals, all the submittal numbers are 1 because on the Procore side, the spec section is prepended (making it look to the user like 303000-1.0).

    When "Number Submittals By Spec Section" is on, the API should include the spec section in the submittal number, or we should be able to read the value of Number Submittals By Spec Section from the API so we know we need to add it.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow partial assignments of resources on project schedules

    Allow partial assignment of resources on project schedules. 3rd party programs like MS Project support partial assignments and this data mapping should flow through.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support for file/attachments - multipart.

    It would be a great feature to support ability to POST attachments. This is an important business case where legal documents, immediate reference point policy documents, hazard or even work site incident document tied to user can be uploaded via API

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  16. Make "Closed Date" Available in Punch List API

    In the web client, if a Punch List Item has a status of "Closed", the date it was closed is shown. This date is not available in the API. Please make it available so we can provide the same information as the web client. See attached screenshot.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  17. API - Need to be able to load inactive Vendors and Users the same way we do for Projects now

    Right now we can load projects and get active and inactive ones using a filter. This is super helpful.
    But we cannot load inactive vendors in a similar manner. There is an API endpoint to load the, but what we get back is "vendors lite", missing key fields such as origin_id. The only way to get origin_id is to re-active each vendor and then load it, and then set it back to inactive -- a terrible solution!
    Please please please, make this work exactly the same way as project - allow us to pass in a filter asking to include…

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  18. Create a "Budget Snapshots" API endpoint

    Please enable a budget snapshots endpoint, would be extremely valuable. We use this feature for month-end reporting and performance reviews.

    9 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  19. Be able to use List Images endpoint to return images within multiple albums

    List Images currently lists all images in a single album (image_category_id). Would allow for greater optimization if you were able to get images from multiple albums with one call by passing multiple image_category_ids.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  20. Be able to read, write update Prime Payment applications

    Why is the Prime Payment Application API different from the new Requisition API? There are no Origin IDs, we cannot read the contract and change lines, et cetera. Let's not have two different ways of interacting with requisitions. Prime is sorely lacking now.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Developer Feedback for Procore Connect API and Developer Portal

Feedback and Knowledge Base