RP04PSC09 = Second filing for the withdrawal of a person with significant control statement
action_date - seems this field isn’t documented yet in e.g. filingHistoryList but it’s been appearing for a while.
Across the CH API it sometimes occurs that fields - especially dates - are null or have odd values. Probably worth adding a quick sanity check on any date / number. See e.g. http://forum.aws.chdev.org/t/null-values-for-values-fields/988
My observations:
Beta doesn’t have a problem with these (this field isn’t used there?).
Here are a few examples of items from filingHistoryList resources where nulls are returned as described in the OP:
(some fields cut for clarity - ‘…’):
One:
{
“links”:
{
“self”: “/company/09232291/filing-history/MzE4MjY1OTYwNGFkaXF6a2N4”,
…
},
“type”: “RP04PSC09”,
“action_date”: null,
“description_values”:
{
“withdrawal_date”: null
},
“description”: “second-filing-withdrawal-of-a-person-with-significant-control-statement”,
…
},
Two:
{
“description_values”: {
“withdrawal_date”: null
},
“links”: {
“self”: “/company/01679488/filing-history/MzE4MjY1NjE2M2FkaXF6a2N4”,
…
},
“type”: “RP04PSC09”,
“action_date”: null,
…
},
Three
{
“description_values”: {
“withdrawal_date”: null
},
“action_date”: null,
“type”: “RP04PSC09”,
“links”: {
“self”: “/company/00675312/filing-history/MzE4MjY2NTMwNmFkaXF6a2N4”,
…
},
…
},
Four:
{
“action_date”: null,
“type”: “RP04PSC09”,
“links”: {
“self”: “/company/05886419/filing-history/MzE4Mjg3NTQ2MGFkaXF6a2N4”,
…
},
“description_values”: {
“withdrawal_date”: null
},
…
},