When you look in the settings of the add on ($yourforum/admin.php?options/groups/zeeBotGuard/) you'll find, that there is a whitelist for IPs that you can use (under "Excluded IPs/CIDRs/ASNs") as well as the option for trusted reverse dns ("Additional trusted crawler reverse DNS domains") as well as the option to exclude rss feeds (Exclude RSS/Atom feeds from protected areas) as well as the option to exclude certain paths (which could be your API) under (Excluded paths and routes).Hi,
First of all great add-on which has really helped with the bots and my site crashing.
One question though, I have an API key so the resources on my site had be added automatically to a website.
I had this message from the person which managed the site via the API key - Is there anyway around this?
If you did not realize any of that you obviously did not look into the settings of the add on and neither in the FAQ for the resource / add on nor in the (pretty excellent) documentation of the add on. All of which was created to avoid trouble and unneccesary support requests for a free add on. Which, as a side note, leaves the question if you really should run an add on of the complexity of Bot Guard if you do not in the slightest care what it does and what it's options and boundaries are...
The Faq states:
Will it break login, registration, APIs, webhooks, or payment callbacks?
Default exclusions are designed to avoid that.
Admin, login, register, API, webhook-style paths, CAPTCHA, static assets, robots.txt, sitemap-style paths, and similar sensitive routes are excluded by default. Custom third-party endpoints should still be reviewed and explicitly excluded when needed.
As you say
but do not bother to say what kind of API you are using it is pretty impossible to answer to your issue in a useful way anyway. I'd recommend going through the options and docs listed above - it seems that there are plenty of options to solve your issue.I have an API key so the resources on my site had be added automatically to a website.