kw917
New Contributor II
Joined 4 years ago
User Profile
User Widgets
Contributions
No Pagination Support on REST Post Snap?
Hi everyone, I am using the REST Get snap and it works beautifully for paginated data requests (using the Has Next boolean field and the Next URL field). I noticed that for some strange reason the REST Post counter-part snap doesn’t have this functionality. Even though it is less common to hit an HTTP POST endpoint for pagination purposes, I have several APIs that we need to get into production that require a POST and pagination. Could this functionality being added using the same logic and code (for re-use / lower LOE)? @mbowen who has exceptionally good news for me on my other question last month. Thanks in advance! P.S. I am getting access to Snaplogic support directly and will likely be able to open tickets and feature requests but I am kind of secondary for our company in terms of vendor feature requests, so I think the forum is appropriate. If you need our lead Snaplogic aligned contacts to open a formal feature request, please let me know. Kurt3.9KViews2likes5CommentsRe: How to log the Raw request sent by HTTP Get snap to end point?
Hi @mbowen - this is so great to hear! I wasn’t even sure if a post this old would be monitored and was planning to reach out via our CSM in a week or two if I didn’t hear back. Appreciate the quick reply and good news. Much appreciated – how will we find out about this new feature as it potentially approaches being released? Thank you, Kurt1.7KViews0likes1CommentRe: How to log the Raw request sent by HTTP Get snap to end point?
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. Kurt1.7KViews1like1Comment