# 500 on diverse API calls

**URL:** <https://community.hubspot.com/t/500-on-diverse-api-calls/13615>\
**Category:** APIs & Integrations\
**Tags:** developer-tools\
**Created:** [March 21, 2019, 11:16am UTC](https://community.hubspot.com/t/500-on-diverse-api-calls/13615 "2019-03-21T11:16:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ArnaudP](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/arnaudp/32/18373_2.png) [@ArnaudP](https://community.hubspot.com/u/ArnaudP)\
**Post date:** [March 21, 2019, 11:16am UTC](https://community.hubspot.com/t/500-on-diverse-api-calls/13615/1 "2019-03-21T11:16:39Z")

</div>

Hello,

I am experiencing 500 times to times (almost every day). The response body looks like that:

`{"status":"error","message":"internal error","correlationId":"36a6f043-78d6-4a9d-9bd6-a19fe1a25430","requestId":"7e46840b75e61da3361986e1a7f8d7c2"}`

The endpoints on which it happens are:

/contacts/v1/contact/createOrUpdate/email/:email

/deals/v1/deal/paged

I have no idea how I can debug these

---

<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 22, 2019, 4:17pm UTC](https://community.hubspot.com/t/500-on-diverse-api-calls/13615/2 "2019-03-22T16:17:10Z")

</div>

Hi, @ArnaudP.

To be transparent, `500` errors are very difficult for us to troubleshoot as well, so I don’t know how much help I can lend here.

When you retry these requests, do they go through successfully? The `500` errors we see with our APIs are often transient and can be due to traffic at certain endpoints.

---

<div class="post-metadata">

**Author:** ![ArnaudP](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/arnaudp/32/18373_2.png) [@ArnaudP](https://community.hubspot.com/u/ArnaudP)\
**Post date:** [March 24, 2019, 9:55am UTC](https://community.hubspot.com/t/500-on-diverse-api-calls/13615/3 "2019-03-24T09:55:14Z")

</div>

I haven’t

My guess is that we reach API limit rate, which might be not handled the same way in every endpoints, and some are returning 500s instead of a clear message. The reason I think that is because we have limit rate errors on other endpoints as well

We haven’t implemented a retry mecanism so far so I don’t know if the exact same requests can pass. But I assume that it’s the case because most of the requests don’t fail

---

<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 25, 2019, 12:30pm UTC](https://community.hubspot.com/t/500-on-diverse-api-calls/13615/4 "2019-03-25T12:30:45Z")

</div>

Thanks for clarifying, @ArnaudP.

It’s possible that endpoints have different ways of handling rate limits, however I haven’t seen any evidence of this in the past.

All successful requests should return `X-HubSpot-RateLimit-...` headers detailing your account’s limits and consumption. If you exceed those limits, all endpoints should return `429` errors. Read more in [this article](https://developers.hubspot.com/docs/faq/working-within-the-hubspot-api-rate-limits).

I recommend retrying requests first — the vast majority should succeed. If you’re seeing patterns of failure with various endpoints, though, please let me know.