Details of request “Crypto Currency Related Complaints

Event history

This table shows the technical details of the internal events that happened to this request on 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.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on 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 created_at described_state last_described_at calculated_state link
50146  sent  2019-05-09 14:44:44 +0200  waiting_response  2019-05-09 14:44:44 +0200  waiting_response  outgoing  
55413  overdue  2019-06-04 00:00:00 +0200         
50877  followup_sent  2019-06-04 15:22:30 +0200        outgoing  
57918  very_overdue  2019-06-26 00:00:00 +0200         
58049  followup_sent  2019-07-05 10:17:01 +0200  internal_review  2019-07-05 10:17:01 +0200  internal_review  outgoing  
68578  edit  2020-01-06 04:45:17 +0100         
68579  edit  2020-01-06 04:45:17 +0100         
68580  edit  2020-01-06 04:45:17 +0100         
68581  edit  2020-01-06 04:45:17 +0100         
68582  edit  2020-01-06 04:45:17 +0100         

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 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.