Page History
...
This same code could be copied anywhere and adapted as needed (e.g., change the name of the header field or check for a specific field value). APIs can now be easily debugged without impacting regular API calls.
Examining the Log Files
While not the same as using the Debugger in an interactive manner, the log files can provide an abundance of useful information. For instance, the entire OECGI request array is maintained in each Request log. This is structured so it is easy to review (read: delimiters are replaced with human readable formatting). The entire response (with some useful metadata) is maintained in each Response log. Furthermore, depending upon how your Debugger Setting is configured, runtime errors will appear in a Debugger, Aborted, or GetStatus log. If you already know some details about a specific request that you need to investigate (e.g., status code, date/time range, endpoint, etc.) you can quickly find the relevant logs using the HTTP Logs utility (just launch the NDW_HTTP_LOGS form):
