I know that this hasn’t been reviewed in a few years but I just want to upvote the need for this functionality. Without trying to be too blunt, it is actually a little ridiculous that an enterprise tool like Snaplogic doesn’t have the ability to inspect the HTTP requests that are being generated by, for example, the REST GET Snap.
In my case, I am using the REST GET snap and the native pagination and everything looks like it would be calculating perfectly with the limit + offset and has next. But the output of what I’m getting back for documents shows a different story.
I need to be able to inspect the HTTP request input through the Snaplogic console. As it stands, I cannot even inspect the requests that are being made in a developer console because they seem to be wrapped/obfuscated.
I would expect that any enterprise product that deals with fetching data via REST would be able to allow the customer to inspect the HTTP request and not just the response. Looking for what the Service URL / URI has become after being dynamically calculated (partially possible), what the HTTP headers were, what the query parameters were, what the payload/body is if a POST request, etc.
What do we need to do to have this feature request re-considered?
Please let me know if I need to elaborate or escalate through our company contacts.
Hi @kw917
Let me assure you that this feature doesn’t need to be re-considered and is very much on our radar. Everything you mentioned are absolutely valid points.
For our SOAP Execute snap, we offer a debug view which dumps the raw SOAP request. This has been super helpful in debugging SOAP issues. I’m not sure that we will do exactly this for our REST snaps, but it may be something similar.
What I can’t guarantee is exactly when, but it may be sooner than you think. I don’t think it is necessary to escalate on your end, but you certainly can if you want. It’s a little embarrassing that you’re replying to a 4 year old thread, but this is actively being discussed!
