Request for Incremental Data Support in API

Hi ,
We would like to request your support regarding the API data retrieval. Currently, when we use the updated_at property, the filter is not working as expected and the data is not being fetched properly.

To address this, we require incremental data support on the API side so that we can fetch data within a specific date range (e.g., a 14-day period). Moreover, we are using GET method for fetching details.

Kindly let us know if this can be enabled or if there are alternative approaches we should follow. Attaching the API link and screenshot for your reference.
API link-https://api.hubapi.com/crm/v3/objects/contacts?limit=10 &properties=firstname,lastname,email,phone,hubspot_owner_id,jobtitle,notes_last_updated,last_contacted,last_engagement_date,last_marketing_email_click_date,last_marketing_email_name,last_marketing_email_open_date,last_marketing_email_reply_date,last_marketing_email_send_date,last_modified_date,last_nps_survey_comment,hs_lead_status,marketing_contact_status,annualrevenue&associations=contacts,companies,deals,tasks,calls,meetings,notes,emails&filter=updatedAt gt 2025-09-01 updatedAt le 2025-10-01

Hi @pglobtest,

You should be able to achieve this by using the CRM Search API.

In the body, you can apply multiple filters to customize your date range. Also, since “updatedAt” is not an actual property, the “lastmodifieddate” property should be used instead in this case.

Sample request below:

{
 "filterGroups": [
 {
 "filters": [
 {
 "propertyName": "lastmodifieddate",
 "operator": "GT",
 "value": "2025-09-01"
 },
 {
 "propertyName": "lastmodifieddate",
 "operator": "LTE",
 "value": "2025-10-01"
 }
 ]
 }
 ],
 "properties": [
 "lastmodifieddate",
 "firstname",
 "lastname",
 "email"
 ]
}

Hi Evaldas,
Thank you for sharing the solution. The solution you provided is in the POST method request; it is not working on our side. Could you please share a more detailed GET method example for retrieving data based on a date filter?
This will help us move forward with the implementation.
Best Regards
KAT

Hi KAT,

Confirming that the example POST request is working properly and I am able to retrieve results by using that.

Can you share what response you are getting after making the API call?

Hi ,
Kindly check this is the result getting after calling the API. Would be better if you could check with the GET method for the solution, or any other which will give accurate result.
[cid:8e14162b-5be4-4554-8bb7-c2516a7a6bcc]
Best Regards
KAT

Hi KAT,

That looks like an incomplete response, there should be more than that string. If you can provide the full response, it would help trying to resolve what the error could be.

If you can’t, then you can try using HubSpot’s documentation interactive feature that let’s you try an API call and could generate the response as well:

There currently isn’t an option to search for contact records based on property values with the GET endpoint.

Hey @pglobtest - thanks for posting in the Community!
Would you mind confirming whether or not @evaldas 's suggestion solved for the issue here?
Shane, Community Manager

Hi Evaldas,
Kindly check this is the full response result getting after calling the API. We are using the current year date filter, but it is giving previous year. Would be better if you could check with the GET method for the solution, which will give accurate result. Kindly check the screenshot attached.
API using - https://api.hubapi.com/crm/v3/objects/contacts?limit=10&properties=firstname,lastname,email,pho…<> {“filterGroups”: [{“filters”: [{“propertyName”: “lastmodifieddate”,“operator”: “GT”, “value”: “2025-09-01” },“propertyName”: “lastmodifieddate”, “operator”: “LTE”,“value”: “2025-10-01”}]}], “properties”: [ “lastmodifieddate”,“firstname”,“lastname”,“email”]}
Best Regards
KAT
[cid:d66f6b95-484d-458b-b083-c3338993cd4f]

Hi KAT,

As I had mentioned in the previous response, there aren’t any options to retrieve contact records within a date range with a GET method.

Can you try providing the screenshot again? Does not look like it was included.

I also tested the POST call with this filter setup and results come back properly within the date range that they have been last modified (not when they were created). Just make sure that all the syntax is correct, as there were some curly braces missing in the second filter (for the end date).