How to view actual outgoing HTTP Request Headers from REST Connector PostCall?

  • Deniz
    Participant
      3 days, 4 hours ago #66282

      Hi Simplifier Community,

      I’m trying to debug a REST PostCall to an external OData API (IFS Cloud) and suspect an issue with the outgoing HTTP headers, specifically the Content-Type. My connector call is configured with Format: JSON, and in my script, I’m attempting to set Content-Type: “application/json;IEEE754Compatible=true” via the Headers object parameter.

      Despite the payload body seeming correct, I’m getting a persistent API error from the target system (400 – Invalid value for property ‘BuyUnitPrice’).

      I need to verify the exact headers Simplifier is sending. I saw an older forum comment mentioning: “if you active the trace on the http-client you can see the request headers in the Backend log.”

      Could someone explain how to enable this kind of trace for the REST connector’s HTTP client, or suggest another way to inspect the final outgoing request headers from Simplifier?

      Thanks for any pointers!

      Armin Winkler
      Moderator
        Has successfully completed the online course Introduction
        Has successfully completed the online course Intermediate (200)
        Has successfully completed the online course Advanced (300)
        Has successfully completed the online course Basics (100)
      5 hours, 56 minutes ago #66639
      Up
      0
      Down
      ::

      Hi Deniz,

       

      you should be able to see the full REST request details in Simplifier’s ‘Monitoring’ function inside of the tab named ‘Logs‘. When you execute a REST connector call, this should create a new log entry which gets written on log level ‘INFO’. In the table row, please click on the ‘i’ icon under the ‘Details’ column to make the details appear inside of a popover. In case you can’t see the entry row at all, please verify first whether your system has log entries activated on that particular level as configured in the Log settings.

       

      Manually setting the content type for a REST connector call via header parameter should be possible if you are using a current server release (available since release 8 EHP 1), however I think the OData definition requires you to submit the ‘IEEE754Compatible’ flag via the ‘$format’ query parameter instead. Please have a look at their documentation, which is where I also got my information from.

       

      Please let us know if this helps you to finish setting up your OData request via Simplifier’s REST connector.

       

      Kind regards,

      Armin

      • This reply was modified 5 hours, 50 minutes ago by Armin Winkler.
      • This reply was modified 5 hours, 49 minutes ago by Armin Winkler.
    Viewing 2 posts - 1 through 2 (of 2 total)

    You must be logged in to reply to this topic.