Export API not supported anymore as per docs

[alienvault-otx]

Export API not supported anymore as per docs

[rustybrooks]

I think the easiest thing would be... just try it? If it works then you'll have your answer and if not, that's not a definitive answer but probably indicates it's not there any more.

[rustybrooks]

I haven't worked on OTX for over 2 years now, so I can't comment on anything that's changed since then and I can't see the code any more.

My memory says that expired should always be present on an indicator - are you sure you only sometimes see it?

expired of null means no expiration

When an indicator is expired, it won't show up in a pulse's indicators, I believe, unless it's specifically requested. I believe the default is to not include them, but I'd have to check.

If the expiration is changed from null to some value then it will be available through the expiration parameter. Maybe I don't understand what you're asking.

[kcreddy]

Actually its still working even though not present in the official API doc. But, I am really interested in expiration time of indicators, hence would like to use /api/v1/pulses/subscribed.

[kcreddy]

@rustybrooks, I have few questions on expiration field contained inside /api/v1/pulses/subscribed response

1. This field is not always populated and is sometimes null. Does that mean the indicator is never expired?
2. If the indicator is supposed to be expired at some point, but the value returned from the API is still null, is there any default expiration values that you would propose/suggest to end users?
3. If the expiration value of the indicator is modified from null to some date-time value, is this updated value available through the API via pulse's modified_since parameter?

[kcreddy]

Thanks for the details!