# Intermittent Error in ContactList API for large data

**URL:** <https://community.hubspot.com/t/intermittent-error-in-contactlist-api-for-large-data/13297>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [March 1, 2019, 10:21am UTC](https://community.hubspot.com/t/intermittent-error-in-contactlist-api-for-large-data/13297 "2019-03-01T10:21:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fivetran](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/fivetran/32/33328_2.png) [@Fivetran](https://community.hubspot.com/u/Fivetran)\
**Post date:** [March 1, 2019, 10:21am UTC](https://community.hubspot.com/t/intermittent-error-in-contactlist-api-for-large-data/13297/1 "2019-03-01T10:21:31Z")

</div>

While fetching the data from following endpoint ,

`https://api.hubapi.com/contacts/v1/lists/{id}/contacts/all`

we intermittently get **java.net.SocketException: Connection reset** or **HTTP 500** errors. The same endpoint gives us the entire data after couple of retries but generally it doesn’t always work in first go.  
We suspect that large volume of data is partially responsible for these errors at your side. Can you invetigate this further and let us know about any alternatives or best practices to avoid this?  
Thanks!

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [March 4, 2019, 8:43pm UTC](https://community.hubspot.com/t/intermittent-error-in-contactlist-api-for-large-data/13297/2 "2019-03-04T20:43:52Z")

</div>

Hi, @Fivetran.

I’m happy to take a closer look. Can you confirm whether your Hub ID ends in “3379” and share some of the list IDs for which you frequently encounter these errors?

Depending on the size of these lists, there may not be anything _you_ can do to avoid these errors. That said, this is still valuable feedback and I’ll be sure to share it with the relevant team so that we can continue to scale our systems to meet your performance needs.