Public API blocking access

Hi All,

I am making an API call to this endpoint: https://www.asx.com.au/asx/1/company/nab/announcements?count=5&market_sensitive=false

It’s an open public API that I was using with no issues for years but suddenly they must have put in place a spam filter or something that blocked access from other platforms.

If you use the browser to make the call, it work fine. But if I use Make or other platforms to make the call, it’s blocked. See below response.

Is there a way to trick the API to let Make through?

Data

Hello,

Can you run the Make devtool and see what errors/block messages/HTTP status codes are you receiving?

If you have the Make DevTool Chrome extension installed, you should be able to view the request and response headers and body from each module when you manually run the scenario.

From the Help Center article about the Make DevTool:

Make DevTool allows you to debug your Make scenarios in a completely new way. It adds an extra pane to the Chrome Developer Tools. Using this new debugger pane, you’re able to check all the manual runs of your scenario, review all the performed operations and see the details of every API call performed. It also brings a whole bunch of new opportunities for Apps development. You’re able to check every call that your app has performed. Thanks to this extension, you can easily debug your scenario, see which module, operation, even which single response causes the error, and then get your scenario back on track. Try it out and let your scenarios shine!

For more information on how to install and use this, see https://www.make.com/en/help/scenarios/integromat-devtool

2 Likes

Hi @samliew

Status code is 200
Response header

{
“content-type”: “text/html”,
“cache-control”: “no-cache, no-store”,
“connection”: “close”,
“content-length”: “212”,
“x-iinfo”: “8-14497220-0 0NNN RT(1707464777435 10) q(0 -1 -1 1) r(0 -1) B10(4,289,0) U24”,
“strict-transport-security”: “max-age=31536000; includeSubDomains”,
“set-cookie”: [
“visid_incap_2835827=CE0PRtVGQny1OmX3EQKSZUnYxWUAAAAAQUIPAAAAAADambOXbf784f92E/AuM7GZ; expires=Sat, 08 Feb 2025 06:30:20 GMT; HttpOnly; path=/; Domain=.asx.com.au; Secure; SameSite=None”,
“incap_ses_1459_2835827=PiA0AT/h9mibIysEkmk/FEnYxWUAAAAAp+oXZFUoL7Bvig6Mm1C0Qw==; path=/; Domain=.asx.com.au; Secure; SameSite=None”
]

Request unsuccessful. Incapsula incident - suggests a block by the endpoint?

You might have to use a scraping API to bypass it.

Try

These can possibly run in a “real browser” instance, so you are less likely to be detected as a bot.

Personally I like ScrapeNinja, and am using it.

Putting your URL into the scraping tester (select real browser) ScrapeNinja Live Sandbox, shows that they can successfully get the API.

1 Like