Stopping specific bots from using your monthly ShipperHQ quota with nginx

A co-worker of mine recently brought up an issue to me where one of our clients were exceeding their monthly ShipperHQ api quota. The wordpress site in question was exceeding their 10k api limit from ShipperHQ for 2 months in a row. The combined traffic and sales from the site did not justify hitting 10k api calls monthly. This is where I came in to see if there was a deeper issue.

My first steps were to identify when the api call was sent to ShipperHQ on the site. After some navigating though some pages and keeping an eye on the network tab. I determined the call was being sent out when visiting the checkout.
With that known it was time to see where the hits were coming from.

If your are unable to modify your nginx conf. Another option would be to have shipping calculation on a different page.

Or, using jQuery, to only load the ShipperHQ calculations after the shipping address is filled out.

Related posts:

Nella hall della scuola guardo la legenda, tra le altre cose leggo: “livelli di difficoltà, scegliete il vostro, 1=facile, 2=medio, 3=difficile”. Con i libri sotto braccio mi avvicino all’aula di…

When I joined Medium, there was an overwhelming consensus that writing every day will help you grow as a writer. As an obedient student to my craft, I followed their advice and wrote every day. I’ll…

News is shared all over the internet today. Some of it is accurate and some of it isn’t. With the many different apps around today, blogs and news outlets choosing where to get your news may be…