Not receiving JSON result for an API Call

[thms]

In an API step where I get prices for domains, I am expecting a result in the format:

I have simple response DISABLED and I'm expecting a JSON result so that I can iterate through it and filter out just the TLD I want (let's say .net) in this case.

However, I'm getting a SIMPLE response back, formatted by Pabbly.

Any clues as to why?
Or solutions on how to filter this down so that I can get costs for just the one TLD I want (let's say .com)? The API itself does not allow me to send a TLD so that I can get just a filtered response.

 

[ArshilAhmad]

Hi @thms,

Please share the API documentation of the application from which you are trying to capture the response.

 

[thms]

It's hidden behind a login I believe.
https://www.namesilo.com/api-reference#account/get-prices is the link in case you want to try.

Please see the full page here:

 

[ArshilAhmad]

Could you please record and share a video with us showing how the responses appear in Postman?

 

[thms]

Video available at https://tutorials.kitetech.ca/recordings/wexHPKZWYz2VGVXCmRCX

The results appear identical to screenshot above. See screenshot below for results from Postman

 

[ArshilAhmad]

Please grant me access to your workflow by adding me as a team member. This will allow me to gain a better understanding of your issue.
Once you have added me as a Team Member, do let us know the name of your workflow.
Email: [email protected]
Also, remember to revoke access once your query has been resolved.

Attaching a video for your reference:

 

[thms]

added. "Register Domains Through API"

 

[ArshilAhmad]

Please allow us some time to look into this. I will get back to you with an update soon.

 

[ArshilAhmad]

@thms, The XML response will always be in a key-value pair format as it is received that way from the API.

 

[thms]

Thank you. Are there any suggestions you have to be able to run it through an iterator?

 

[ArshilAhmad]

Without receiving the response in array format, the Iterator will not work. Unfortunately, I don't have any other solution.