I am extracting the filingshistorylist object for the company code 09825890 and am finding that the path to:
leads t a k:v pair
action_date : bigint, the bingint is a 13-digit unix epoch.
This k:v pair is not reported in the documentation, and when it appears elsewhere is of type DATE. Is this a bug or we have to expect that in all leaves of the JSON (associated_filings, annotations, resolutions) the “action_date” key will always contain a BIGINT?
It would be helpful to document this kinf of stuff in the official docs.