Details of request “Agreement of Sale betw City of Trenton and Water Vendors from 2009-2010

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
717387  sent    2023-07-25 12:24:54 -0400  waiting_response  waiting_response  2023-07-25 12:24:54 -0400  outgoing  
717437  response    2023-07-25 15:26:08 -0400        incoming  
717445  response    2023-07-25 15:32:21 -0400        incoming  
717455  response    2023-07-25 16:00:58 -0400        incoming  
729371  response    2023-08-10 19:58:59 -0400        incoming  
733019  response    2023-08-16 14:17:42 -0400        incoming  
733020  response    2023-08-16 14:17:53 -0400        incoming  
733021  response    2023-08-16 14:18:01 -0400        incoming  
733022  response    2023-08-16 14:18:03 -0400    rejected  2026-03-20 16:55:50 -0400  incoming  
858838  edit metadata  allow_new_responses_from  2024-02-17 03:45:07 -0500         
858839  edit metadata  allow_new_responses_from  2024-02-17 03:45:07 -0500         
858840  edit metadata  allow_new_responses_from  2024-02-17 03:45:07 -0500         
858841  edit metadata  allow_new_responses_from  2024-02-17 03:45:07 -0500         
858842  edit metadata  allow_new_responses_from  2024-02-17 03:45:07 -0500         
858843  edit metadata  allow_new_responses_from  2024-02-17 03:45:07 -0500         
858844  edit metadata  allow_new_responses_from  2024-02-17 03:45:07 -0500         
858845  edit metadata  allow_new_responses_from  2024-02-17 03:45:07 -0500         
858846  edit metadata  allow_new_responses_from  2024-02-17 03:45:08 -0500         
1368254  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368255  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368256  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368257  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368258  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368259  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368260  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368261  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368262  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368263  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368264  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368265  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368266  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368267  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368268  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368269  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368270  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1368271  edit metadata  allow_new_responses_from  2025-08-17 03:45:10 -0400         
1567408  status_update  described_state  2026-03-20 16:55:50 -0400  rejected  rejected  2026-03-20 16:55:50 -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.