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. 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 →
  2. Add Vendor Ranking support to API

    The Company Vendor edit page, under Bidding Info, allows the user to rank a vendor from 1-5 stars. Please add read/write support for this property to 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 →
  3. Ability to send email to assignees for created punch item

    Currently there is an API to send all of the unsent punch items to the assignee's, but like in the Procore UI, I'd like to have the option when creating a new punch item to send the emails for just that one. It'd be a bit embarrassing if because of my software, a ton of unsent punch items were sent because of the send all unsent API. Thanks!

    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 →
  4. 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.

    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 →
  5. 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.

    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 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.

    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 →
  7. 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.

    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. 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 →
  9. 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.

    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 →
  10. Provide a specification in OpenAPI/Swagger format for the Procore API

    At the moment it is not possible to easily generate code to interact with the Procore API. We have to look at the docs and manually create a standard spec to generate proxies, or code the client code manually. Would you consider providing a specification file in OpenAPI/Swagger format? That would allow us to generate the client code for the whole API in any language.

    Mario L., Maestro Technologies

    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 →
  11. Allow to check if sub jobs are enabled in project settings

    It would be nice to have an API action that allows to check if sub jobs are enabled in project setting (so they can be used in commitments). It will help to separate cases when sub job is missing or a project just not issues sub jobs at all. In scope of integration with other systems it will help to define if missing sub job should be treated as an exception or replaced with some stub value

    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. API call to Delete Observations

    Given that we can create an observation and attach files to an observation. It would be really nice to be able to delete an observation.

    The workflow I am using is we upload observations based on a users selection of elements. If they were to cancel half way through it would be nice to delete all that work so we don't clutter their workspace.

    Thank you!
    --Tim Hodges

    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 →
  13. 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.

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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 →
  15. Add ability to create service accounts via the API

    For apps that need service accounts (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 account 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 →
  16. 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 →
  17. 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

    3 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 →
  19. 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 →
  20. 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 →
← Previous 1 3
  • Don't see your idea?

Developer Feedback for Procore Connect API and Developer Portal

Feedback and Knowledge Base