# API call limit reached

**URL:** https://community.beestat.io/t/api-call-limit-reached/1706
**Category:** Bug Reports
**Created:** [March 12, 2026, 2:17pm UTC](https://community.beestat.io/t/api-call-limit-reached/1706 "2026-03-12T14:17:38Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Cloud](https://community.beestat.io/letter_avatar_proxy/v4/letter/c/e99b99/32.png) [@Cloud](https://community.beestat.io/u/Cloud)
#### Post date: [March 12, 2026, 2:17pm UTC](https://community.beestat.io/t/api-call-limit-reached/1706/1 "2026-03-12T14:17:39Z")

</div>

See attached. Is this a problem on my end or with beestat? This happened when I was trying to refresh the temp resistance heat cool trend line graph.

 ![IMG_8697](https://community.beestat.io/uploads/default/original/1X/3760159e1ea234bf474666ba59de7c826135b2a7.jpeg)

---

<div class="post-metadata">

### Author: ![ziebelje](https://community.beestat.io/user_avatar/community.beestat.io/ziebelje/32/633_2.png) [@ziebelje](https://community.beestat.io/u/ziebelje)
#### Post date: [March 13, 2026, 10:23am UTC](https://community.beestat.io/t/api-call-limit-reached/1706/2 "2026-03-13T10:23:22Z")

</div>

Looks like a beestat issue - If you email [contact@beestat.io](mailto:contact@beestat.io) with your serial number I can take a closer look. It should resolve itself, so it may not be a major issue unless this happens persistently.

---

<div class="post-metadata">

### Author: ![Cloud](https://community.beestat.io/letter_avatar_proxy/v4/letter/c/e99b99/32.png) [@Cloud](https://community.beestat.io/u/Cloud)
#### Post date: [March 22, 2026, 3:32am UTC](https://community.beestat.io/t/api-call-limit-reached/1706/3 "2026-03-22T03:32:35Z")

</div>

Just emailed you. Sorry for the delay.