With the current endpoint:

PATCH /vapid/cost_codes/sync

We are able to insert multiple cost codes at once which is great!
However, there is a downfall in how it has been built today.

In our integration we would like to built the entire cost code hierachy from scratch using your API but it seems we can only do it using the single-resource endpoint:

POST /vapid/cost_codes

That is because the bulk insert endpoint can not build a proper hierachy with parent_id as they are unknown when uploading!

The way to do it today is to loop over each cost code we want to upload and save the ID we get back, and optionally use that as a parent_id for any other cost code in the loop. This is very cumbersome and not very optimized in regards to speed and efficiency.

I am proposing a new structure for the body for endpoint:

PATCH /vapid/cost_codes/sync

Body Example:

{

   updates: [

   {

       id: 348330,

       position: 1,

       code: 300,

       name: Site Work,

       origin_data: OD-239238,

       origin_id: 3497237,

       parent_id: 12345,

       standard_cost_code_id: 122334,

       children: [

       {

           id: fege,

           origin_id: poekg,

           children: [

           {

               .....

           }

           ]

       }

       ]

   }

   ]

}

This improvement suggestion is directed towards the use of the [Drawings endpoints](https://developers.procore.com/reference/drawings).

Currently, the use of the filtering and sorting of List Actions is [limited to a subset of the available actions](https://developers.procore.com/documentation/filtering-on-list-actions). Some actions that do not have this functionality include the List Drawings and List Drawing Revisions endpoints.

To better improve the performance in uploading drawings from a source system to Procore, it would be beneficial to have the ability to filter drawings in the List Drawings endpoint based on their: number; discipline; revision_number. That is, filter based on their values and not the IDs supplied by Procore. Additionally, having the ability to filter drawing revisions in the List Drawing Revisions endpoint based on their associated drawing number value and not by drawing ID.

This would improve the performance of a client/customer's interaction with the Procore API as, currently, a client must iterate through the list returned by the two mentioned endpoints to determine if a drawing or its revision currently exists. With this filtering ability the client/customer has the reduced need to have to manage pagination and potentially iterating through thousands of drawings in order to identify if a drawing exists or not.

Dear Team,
We could see webhook along with events and deliveries against Procore Namespace alone. Its good that we are able to create more webhooks with different namespace against any folder/ resource name. Also we have API to list down all deliveries against the webhook id with filters. If we can bring UI for that deliveries for all Webhooks, it would be really helpful for IT team at customer end. Development team once handover, we can guide them if any issues in deliveries what request and what response received from development application.
Features:
1.List of webhook along with link
2.Once clicked able to view the events with filters Any/ success/ failed

End users can able to view those request for tracking or failure tracking.

Regards,
Venkatesh S S

P.S-Right now we are able to view only Procore namespace webhook.

Maintain the SOV order of cost codes. Keep the option to move line items as needed. If Prime Contract has an SOV or a CE is entered with an SOV list, please maintain the same order while moving on to the next screen. Don't jumble my cost codes and expect me to reorganize for every printout. A direct link to the Prime Contract SOV is an option but not the ultimate answer because often while negotiating we may issue a zero dollar Prime Contract and add the SOV in full or portions via owner change order(s). However, maintain the option to move line items because some people present insurance or final clean as a line item at the top of the list in numerical order, some people group those items into general conditions and others may drag the insurance line to the bottom but keep separate from general conditions. Allow options but keep continuity!