@AdKerremans While there may be a better way to tackle this request, we have a process that first retrieves the full list of properties from HubSpot (GET /crm/v3/properties/{objectType}) and saves those to a database table. We then aggregate all of the rows into a single comma-separated string and call the Contacts API endpoint (search, get specific contact, etc) and concatenate that comma separated list of properties in the request body. This pulls back all contacts that meet our criteria along with all of the current properties in HubSpot.
From there we save the results to a file and parse out specific properties to load to our database tables.
@AdKerremans While there may be a better way to tackle this request, we have a process that first retrieves the full list of properties from HubSpot (GET /crm/v3/properties/{objectType}) and saves those to a database table. We then aggregate all of the rows into a single comma-separated string and call the Contacts API endpoint (search, get specific contact, etc) and concatenate that comma separated list of properties in the request body. This pulls back all contacts that meet our criteria along with all of the current properties in HubSpot.
From there we save the results to a file and parse out specific properties to load to our database tables.