Details of request “Code Violation List Request

Event history

This table shows the technical details of the internal events that happened to this request on OPRAmachine. This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Be careful! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on OPRAmachine. How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand FOI law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type details created_at described_state calculated_state last_described_at link
1341352  sent    2025-07-22 08:01:24 -0400  waiting_response  waiting_response  2025-07-22 08:01:24 -0400  outgoing  
1341398  response    2025-07-22 09:33:27 -0400    waiting_response  2025-08-04 01:43:52 -0400  incoming  
1354928  overdue    2025-08-01 00:00:00 -0400         
1353753  status_update    2025-08-04 01:43:52 -0400  waiting_response  waiting_response  2025-08-04 01:43:52 -0400   
1362794  response    2025-08-11 16:52:46 -0400    waiting_response  2025-08-18 03:40:12 -0400  incoming  
1368669  status_update    2025-08-18 03:40:12 -0400  waiting_response  waiting_response  2025-08-18 03:40:12 -0400   
1369722  response    2025-08-18 10:58:03 -0400    waiting_response  2025-08-26 03:25:18 -0400  incoming  
1375752  very_overdue    2025-08-20 00:00:00 -0400         
1375163  status_update    2025-08-26 03:25:18 -0400  waiting_response  waiting_response  2025-08-26 03:25:18 -0400   
1375787  response    2025-08-26 09:29:39 -0400    waiting_response  2025-08-29 02:48:57 -0400  incoming  
1377174  status_update    2025-08-29 02:48:57 -0400  waiting_response  waiting_response  2025-08-29 02:48:57 -0400   
1389701  response    2025-09-05 14:41:41 -0400        incoming  
1396807  response    2025-09-08 15:49:19 -0400    successful  2025-09-16 09:16:09 -0400  incoming  
1408727  status_update  described_state  2025-09-16 09:16:09 -0400  successful  successful  2025-09-16 09:16:09 -0400   
1563640  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563641  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563642  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563643  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563644  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563645  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563646  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563647  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563648  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563649  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563650  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563651  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563652  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         
1563653  edit metadata  allow_new_responses_from  2026-03-17 03:45:08 -0400         

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by OPRAmachine for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.