Modify API to include enabled/disabled status for `/api/v1/committees/`

[exalate-issue-sync]

Modify API to include enabled/disabled status for /api/v1/committees/

Current example output

{
"count": 123,
"next": "http://api.example.org/accounts/?page=4",
"previous": "http://api.example.org/accounts/?page=2",
"results": [
{
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"deleted": "2026-03-17T14:00:08.291Z",
"committee_id": "C03691570",
"created": "2026-03-17T14:00:08.291Z",
"updated": "2026-03-17T14:00:08.291Z",
"members": [
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
]
}
]
}

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-2954

[exalate-issue-sync]

Dan Fowlkes commented: What am I missing here?

I get back “disabled” already when I hit {{/api/v1/committees/}}, returned as null or a timestamp much like “deleted”.

Something interesting that I noted, though:

• disabling a committee to which I have access logs me out
• when I log back in, the disabled committee is still shown in “Select a committee account” (<-- I suspect this is a bug)
• clicking the disabled committee logs me out again

[exalate-issue-sync]

Todd Lees commented: Testing and confirmation done by [~accountid:712020:3a738b19-6415-43b4-81c1-e92f1f7586f3] in comment below