After a few more hours of digging and trying various things, I found what the issue was. In my original picture I was using a path with http:// . This http:// was redirecting to an https:// path automatically from a 301 redirect response. However, by default, Postman will automatically redirect the response and convert the original HTML request to GET instead of PUT or POST, removing the body of the request. This is what was causing a error response that looked like I was missing record_no information, even though clearly it was in the original request.
This behavior makes sense as its meant to prevent sending data to an unknown source if its redirected without your knowing. However, as someone not familiar with POSTMAN, I did not realize this was happening until I turned off automatically follow redirects, and found that I was getting a response to redirect me at the https version of our site. See below picture for reference.
Ray McEntee -Oracle - Any way this can be noted in integration documentation? I know this redirect may only be applicable for cloud hosted environments, however it seems worth noting as this was a pain to troubleshoot, and going through searches on the community I found one other individual who had this same problem about a year ago without any resolution from the community.