# API JSON Endpoint working on dev, but not prod

**URL:** <https://forums.losant.com/t/api-json-endpoint-working-on-dev-but-not-prod/5481>\
**Category:** Help\
**Tags:** experience, workflow\
**Created:** [May 23, 2024, 10:29pm UTC](https://forums.losant.com/t/api-json-endpoint-working-on-dev-but-not-prod/5481 "2024-05-23T22:29:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Calibey](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/nick_calibey/32/4628_2.png) [@Nick\_Calibey](https://forums.losant.com/u/Nick_Calibey)\
**Post date:** [May 23, 2024, 10:29pm UTC](https://forums.losant.com/t/api-json-endpoint-working-on-dev-but-not-prod/5481/1 "2024-05-23T22:29:07Z")

</div>

Hi there,

In my application I’ve send up an endpoint that sends an asynchronous request to an Endpoint when a user visits a page. The data is then returned as JSON and used client-side to power some manipulations of the DOM. Pretty straight forward stuff.

However, while this worked in our `develop` version of the app, it’s getting a 504 Gateway Timeout on prod client-side (so, the browser). What’s even stranger to me is that the Workflow debug logs show that the Endpoint is handling the request and returning the appropriate JSON – so server-side everything seems to be fine. Any idea of what the issue could be? In case this helps, the URLs I use are in the format of `/this/is/the/path/to/my/resource`, so no prefix with the protocol, domain, etc.

Thanks!

---

<div class="post-metadata">

**Author:** ![Dylan\_Schuster](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/dylan_schuster/32/2850_2.png) [@Dylan\_Schuster](https://forums.losant.com/u/Dylan_Schuster)\
**Post date:** [May 24, 2024, 12:09pm UTC](https://forums.losant.com/t/api-json-endpoint-working-on-dev-but-not-prod/5481/2 "2024-05-24T12:09:04Z")

</div>

Can you send me some steps to reproduce the issue? You can PM me this information …

- A URL where the issue is occurring - and, if you have a URL for the develop version where this is working, that too.
- If necessary, please set up an Experience User for us to log in with (you can use [support@losant.com](mailto:support@losant.com)) and send the password via PM.