Sorting of response

[WildDogOne]

Hello Everyone,

I've noticed that the default sorting of the API responses are ascending. This of course makes searching for recent Pulses a pain, I would have to pull huge amounts of data and sort locally, which is an unnecessary strain on the API Would anyone be interested in adding a parameter to sort descending?

Regards,

Linus

[rustybrooks]

Sorting would probably be nice. But something you might find useful is that there is a (newish) class in the SDK called OTXv2Cached. It's roughly identical to OTXv2 but cached results locally. Whenever you run the functions on it, they update your local cache and then operate on the cached data.

There are 2 things you'll want to do:

• it's constructor takes a cache_dir option, you'll probably want to set that to your preferred location
• in your script, at the beginning, you'll want to run the update() function on the class - this updates the cache. So something like

o = OTXv2Cached(API_KEY)
o.upate()
for p in o.getall():
   ... etc

[rustybrooks]

Note that the first time you ever run o.update() it'll take a while to populate everything. Also, if you ever suspect the cache is wrong or corrupted, you can just delete the whole cache directory and the next time you run .update() it'll re-populate it.

[WildDogOne]

that is indeed a nice function, but would still make me download heaps of requests, and I honestly don't want to load the OTX API like that. I will sleep over this and if I have too much time I'll try and commit a fix to this