Hi, have you tried to look into your network configuration? Are you accessing your instance through a reverse proxy or load balancer? If so, try accessing the app server directly to see if it makes any difference.

Hi Anders, and thanks for all the expertise and wisdom you share with our community!

I have tried this. I am on a Windows 2019 server if that is relevant. I have tried this as recently as today making an API call from Postman on the very same computer on which Joget Enterprise version is installed and has been working perfectly with the exception of recognizing these API calls. The same things seems to happen by making the calls from JSON tools as well - 400 - Bad request. In a browser, also on the same computer, URLs with paths as far down as http://localhost:8080/jw/web/ work just fine but adding /json and additional paths below that are not accepted. In particular the API we need is a POST of this form http://localhost:8080/jw/web/json/data/form/store/ifcsnsandbox/grantTerms/001 to create a form record but it will only give a consistent 400 - Bad request. Is there something unique about a Windows installation of Joget that may be involved? The API domain whitelist in Settings is currently * but we have tried many various combinations to no avail. Thanks!