Hi!
I have a question regarding POST calls. I’m working with a (DB2) Thinkwise application that uses tables and views (with instead‑of triggers). We’re trying to perform API calls on these tables, specifically GET and POST calls. The GET requests are successful and return data from both tables and views.
The issue is with the POST requests: I consistently receive a 403 Forbidden response.
Here’s what I have checked so far:
- The POST URL works when used in a GET request.
- The same credentials are used for both GET and POST.
- With these credentials, I can view, edit, delete, and insert data through the application and ACS.
- The application is running on IAM.
- I inserted data through ACS using the same values as in my JSON POST; the ACS insert succeeded, but the POST request returned 403 Forbidden.
- I verified that all mandatory fields are included in the POST body.
What I’ve noticed is this:
POST calls to tables with editable mandatory fields are successful, but POST calls to tables where mandatory fields are set to read‑only or hidden return 403 Forbidden.
Based on this, I suspect the issue is caused by mandatory fields being read‑only or hidden, and that these fields need to be editable for a POST to succeed.
Can you help me with this?
