Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cannot sync properties_with_history in endpoint "/crm/v3/objects/contacts/search"

Open
#244 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by tracing the Python client entry point for /crm/v3/objects/contacts/search and compare its supported parameters with the properties history request described. Done means determining whether the search endpoint can return properties_with_history and documenting or implementing the supported behavior without relying on one company request per contact.

Written by the indexing model from the issue text.

Description

HI every one!
Now, i am using endpoint "/v1/lists/recently_updated/contacts/recent" to sync recently properties but i want using endpoint "/crm/v3/objects/contacts/search" to get lastmodified properties from hubspot.

With issue the endpoint "/crm/v3/objects/contacts/search" cannot get properties_with_history. It''s importance for me to build history of properties.

To fix it:
i am using endpoint "/crm/v3/objects/contacts/search" to get contact_id lastmodified and using endpoint "/crm/v3/objects/companies/{companyId}" to get properties_with_history and this way make system be overloaded because to get the history of the contact_id I have to call the endpoint "/crm/v3/objects/companies/{companyId}" once.

Anyone support me how to get properties_with_history in a easier way
telegram-cloud-photo-size-5-6169973060942281143-y
image

Dominant language
Python
Stars
434
Forks
126
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HubSpot/hubspot-api-python

All issues in HubSpot/hubspot-api-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.