Hello,
I am building an app and making use of Private App and the API documentation that exists.
The number of tickets we have on Hubspot is large, and trying to pull all tickets daily is not what I want. I would prefer a situation whereby I can pull all and sync the tickets created or updated per day at the end of that day to my local DB. How can I limit the returned data by the date created or the date updated?
I think I would use /crm/v3/objects/tickets/search and add a search filter for the create date to get what you want. Accounts Dashboard | HubSpot
search does not exist in the documentation.
https://api.hubapi.com/crm/v3/objects/tickets?properties=team&properties=stage&properties=module&properties=source_type&properties=hs_ticket_category&properties=location&properties=hs_pipeline&properties=ticket_priority&properties=recurring&properties=hs_ticket_id&properties=azure_link&properties=closed_date&properties=createdate&properties=subject&properties=hubspot_team_id&properties=hubspot_owner_id&properties=hs_pipeline_stage&properties=action_s__taken&properties=completion_timeline&properties=hs_ticket_priority&properties=hs_merged_object_ids&properties=hs_primary_company_name&properties=content&properties=time_to_close&properties=hs_time_to_close_sla_status&properties=hs_time_to_close_sla_at&properties=nps_score
Above is the GET request. I want the response limited to where
createdAt = today or updatedAt = today
Hi @DDawodu , totally get your use case pulling the full ticket set daily is heavy and unnecessary.
The /crm/v3/objects/tickets/search endpoint is indeed the right one for incremental pulls, even if it doesn’t appear in the base “objects” docs. You can find it under the CRM Search API
(Search the CRM - HubSpot docs )
You’ll POST to /crm/v3/objects/tickets/search with a filter like:
{
"filterGroups": [
{
"filters": [
{ "propertyName": "createdate", "operator": "GTE", "value": "2025-10-21T00:00:00Z" },
{ "propertyName": "createdate", "operator": "LTE", "value": "2025-10-21T23:59:59Z" }
]
}
]
}
You can swap createdate for hs_lastmodifieddate when syncing updates. This gives you a clean daily delta to store locally instead of paginating through millions of records.
If you need both created and updated changes in one process, a two-way sync layer like Stacksync automates these incremental pulls and writes back updates instantly, so your local DB and HubSpot stay aligned without manual filtering.