Account endpoint for unused addresses returns huge list of transactions

[dcmattb]

For a valid but non-existant/unused address, the API performs a redirect to tx.json, resulting in a huge amount of transaction data.
Example, for the random valid address: rJiiuDYfa7rvkurL2GLUTmjpSHrHeeH49J

curl https://api.xrpscan.com/api/v1/account/rJiiuDYfa7rvkurL2GLUTmjpSHrHeeH49J
returns:
Found. Redirecting to https://data.xrpscan.com/tx.json

If the redirect is followed, the result is a json output including "error" ("actNotFound")
curl -L https://api.xrpscan.com/api/v1/account/rJiiuDYfa7rvkurL2GLUTmjpSHrHeeH49J

{
  "error":
  {
    "status": "error",
     "error": "actNotFound",
     "error_code": 19,
     "error_message": "Account not found."
  },
  "settings": {},
  "transactions":
    [      huge list of 256,000 transactions    ]
}

[pkcs8]

Hi @dcmattb apologies for this. This API endpoint is intentionally designed this way to prevent abuse. We're getting a huge number of requests from group of IPs that query random valid address in the hope of landing upon an active account with positive balance.

To get around this tripwire, I suggest you check the HTTP response's status code and set your client to not follow any 301s.

Can you please let me know how you're landing up in this state? The tripwire activates only after a predefined number of random account requests.

[dcmattb]

Ah, thanks for the explanation! I was using a script to check a wallet for balances which would generate the first 20 addresses from seed words and check them for balance. I've probably run it a few times in quick sucession for debugging. I'm not randomly chancing it (the odds would be ridiculous - I don't know why anyone would do this); these are real seed words I wish to check for ripple, but I see now how this could activate the tripwire.