This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
here are a whole host of tools out there that allow you to monitor the web-calls made when you hit 'submit' or refresh a page. The easiest way to do this is to right click and hit 'Inspect', a console will open on the right side, navigate to the 'network' tab and then hit 'XHR'. When you next load the page which contains the data you want, the console will populate with the web calls that are being made.
From this, it may be possible to decipher the calls made and convert this into an Alteryx workflow. In this instance that seems like it could be possible; the images below provide some detail on why I believe that to be the case...
So you can see a POST request is being made...
The reason a POST request is being made rather than a traditional GET is it seems that what you check on the 'search' menu is being used to query the data, this stuff would represent your 'body'. If you choose 'View Source', this is the structure you should use for your body.
Another key piece when performing web-scraping are your headers, now not all of these will be necessary. Traditionally, if you are performing a POST requesst, then the 'Content-Type' is the most important header, as that informs how the body is structured.
In theory, you should be able to get this to work with this information, but, it may be quite tedious and there are no guarantees you will get it to work, but I just wanted to provide this information that it could be possible.