<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Search the CRM API 10,000 objects limit in APIs &amp; Integrations</title>
    <link>https://community.hubspot.com/t5/APIs-Integrations/Search-the-CRM-API-10-000-objects-limit/m-p/365452#M35985</link>
    <description>&lt;P&gt;Hi Wendy,&lt;/P&gt;&lt;P&gt;To share some more context,&lt;/P&gt;&lt;P&gt;Right now, we are paginating as efficiently as possible.&lt;BR /&gt;&lt;BR /&gt;Some of our clients have around a million contacts, and if we just check which of them were modified in the past week, we get around half of them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In order to get 500,000 contacts, with a page limit of 100, we need to make 5000 requests to your server. (per user!)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This means that we can't give this to our customers in real-time, and instead, have to store everything in our databases.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Instead, we just ask that you could dump the entire contacts, maybe even as a gzip-compressed JSON, which we know is less than 10MB in size.&lt;/P&gt;&lt;P&gt;Doing so will save you, and us, so much on bandwidth, both in terms of infrastructure and in terms of speed of data acquisition. It will also make the data for the client more accurate as we could just query a list of contacts as the client needs them, in real-time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd be happy to jump on a call with you or one of your devs to explain our exact strategies, and how supporting this will undoubtedly be smart both for you and for us.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Amit&lt;/P&gt;</description>
    <pubDate>Fri, 28 Aug 2020 08:24:04 GMT</pubDate>
    <dc:creator>AmitMY</dc:creator>
    <dc:date>2020-08-28T08:24:04Z</dc:date>
  </channel>
</rss>

