# Unknown 500s when making smart action API calls

**URL:** <https://community.forestadmin.com/t/unknown-500s-when-making-smart-action-api-calls/362>\
**Category:** Help me!\
**Created:** [May 29, 2020, 8:20pm UTC](https://community.forestadmin.com/t/unknown-500s-when-making-smart-action-api-calls/362 "2020-05-29T20:20:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Suchit\_Agarwal](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/suchit_agarwal/32/271_2.png) [@Suchit\_Agarwal](https://community.forestadmin.com/u/Suchit_Agarwal)\
**Post date:** [May 29, 2020, 8:20pm UTC](https://community.forestadmin.com/t/unknown-500s-when-making-smart-action-api-calls/362/1 "2020-05-29T20:20:44Z")

</div>

API calls are throwing 500s, and not ending up on our backend at all. Please help!

---

<div class="post-metadata">

**Author:** ![arnaud](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/arnaud/32/32_2.png) [@arnaud](https://community.forestadmin.com/u/arnaud)\
**Post date:** [June 2, 2020, 7:24am UTC](https://community.forestadmin.com/t/unknown-500s-when-making-smart-action-api-calls/362/2 "2020-06-02T07:24:24Z")

</div>

Hi @Suchit_Agarwal,  
Welcome in the Forest Admin community!

Unfortunately, we won’t have the chance to help you without a detailed context.

Can you take the time, to write step by step what action you did and what you observed? 🙏  
What are those API calls?  
If they throw 500 HTTP status, you might have explicit backend error logs.

---

<div class="post-metadata">

**Author:** ![Suchit\_Agarwal](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/suchit_agarwal/32/271_2.png) [@Suchit\_Agarwal](https://community.forestadmin.com/u/Suchit_Agarwal)\
**Post date:** [June 2, 2020, 3:00pm UTC](https://community.forestadmin.com/t/unknown-500s-when-making-smart-action-api-calls/362/3 "2020-06-02T15:00:31Z")

</div>

Hi Arnaud  
Sorry about that, I wasn’t sure how much sensitive info I could put in the screenshots here. Thankfully, I figured out the issue, it was an error on our end which was getting lost.

Thanks for checking in.
