djsiegel
Former Employee
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: How do I extract data from an API, using a post request, with the HTTP Client snap?
Ah - its going to depend on the API itself. Likely NO account is required, since you've got a token you're going to pass in a header. I did this recently in an example with monday.com that required only a header being passed. For this, I used the "Secured Headers" type HTTP account, no schema (unless yours requires a specific schema), and just put the needed headers under "Additional auth headers". HTTP Client Config: Secured Headers Account Type configuration:Re: How do I extract data from an API, using a post request, with the HTTP Client snap?
Hi Terrible: This is a pretty common pattern, and I find it easiest just to treat the data from your post like any other data - add a Mapper snap right after your post, and extract the values you need, then use them in the next HTTP Client. I'm attaching a sample pipeline that just uses a free API site URL for testing. In the first HTTP Client, I POST the information you gave, in the Mapper snap that follows, I extract my needed data, and in the other HTTP Client I use those data elements from the Mapper in headers using SnapLogic's ability to evaluate a variable. Hope this helps. Example Pipeline: Mapper pulls out the data we need: Then use those data elements anywhere you need them, whether it's in the URL, in the Query Params, or as Header params, or even in a document posted back:Postman Collection for API Management Functionality
Organizations typically have DevOps procedures and tooling for automation around their legacy microservices or services. SnapLogic has a robust Public API available for those teams to automate publication, versioning, deprecation, migration, and even retirement of both APIs hosted in SnapLogic APIM, and API proxies managed in SnapLogic. We've created a Postman Collection and set of environments that those DevOps teams might leverage to help them manage their APIs in SnapLogic even faster.Re: Generating wrong Json format for empty values
Hi Mohit! What you might try is passing that JSON over to a mapper, and using the mapper to do what you want. Turn off pass through in the mapper and use an expression language statement to convert everything to a string like this: $.mapValues(x=>x == null ? "" : x.toString()) This will essentially set everything to a string, even an empty string. Here’s what my mapper looks like to do this: Hope that gets you closer! – DavidRe: Creating elements out of normalized column data for Gravity Forms
@nsingam : Thank you for your example! That’s a good step-by-step example of how someone can change the format of the data for use elsewhere, and even accommodates the other metadata items 2 and 3. I do happen to really like @koryknick 's example, however, since it leaves the rest of the object intact, and is a very elegant example of the Object.mapKeys() function! His manages to get to the target system format in 2 snaps. It’s pretty neat that we have both a mapKeys and mapValues in our toolbox to use in situations like this. Here’s the sample pipeline that does the transformation. GravityFormsReassemble_2022_07_08.slp (8.8 KB) Thank you both!Creating elements out of normalized column data for Gravity Forms
I’ve got a JSON ‘entry’ (sample below) that’s coming to me from a rest API, and the elements in that entry consist of all the metadata about a form that the users fill out, as well as all their responses. Each of the user’s responses are normalized by Gravity Forms however, by making a numbered element with the response as the value for each element, and the “_labels” element contains the column or field names for each response. To get to my target database however, I want to use those values inside the labels element as keys for the values that are at the top level. I’ve reviewed a couple of posts here from Patrick that do something similar using a double mapping pipeline, and I was able to make my own pipeline using a JSON splitter to get a JSON of just the labels, but I can’t seem to figure out how to pivot or transpose the data to get a tuple to reinsert into the main document. My gut feel is that I need to get the data I want into its own set of documents, then join that to the original. Essentially I’d like to turn the entries for 1.3: into an element like this: "First": "Post", Sample Entry: "entries": [ { "2": "Creating using REST API v2", "3": "Manually created using the POST route of the REST API v2", "id": "311", "form_id": "176", "post_id": null, "date_created": "2018-10-16 12:43:23", "date_updated": "2018-10-16 19:33:56", "is_starred": "0", "is_read": "1", "ip": "::1", "source_url": "http://localhost/wp.dev/?gf_page=preview&id=176", "user_agent": "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0", "currency": "USD", "payment_status": null, "payment_date": null, "payment_amount": null, "payment_method": "", "transaction_id": null, "is_fulfilled": null, "created_by": "1", "transaction_type": null, "status": "active", "1.3": "Post", "1.6": "Entries 2", "1.2": "", "1.4": "", "1.8": "", "_labels": { "1": { "1.2": "Prefix", "1.3": "First", "1.4": "Middle", "1.6": "Last", "1.8": "Suffix" }, "2": "Untitled", "3": "Untitled" } },
