Table of Contents
Technical information
Please find in the page linked below the technical documentation for the Corti public API:
Please note that:
THROTTLING
We do not have any rate limiting, however, we do recommend:
- a maximum of 6 hours per export
- and, waiting for the request to be over before initiating a new one, to not overload the system one request at a time
STRUCTURE
The structure of the JSON request body is a tabular format using a CSV file - very much like the tabular examples provided above.
More on Case and Event metadata
The API documentation has is divided into sections each detailing how to call a specific endpoint.
The section about 'Export Case/Event Metadata' should is the one describing how to get much of the data related to cases metadata.
Case metadata
When exporting Cases metadata, you get a dump of the following data in a tabular format where each row is a case. See below an example of a row:
The column header with a $ are metadata originated in Corti, while the headers without it are custom metadata imported from external sources (i.e. CAD)
Please find here an example list of all the cases endpoints (column headers)
- Case endpoints: $case_id, $created_at, $latitude, $longitude, $dispatcher_name, $gender, $phone, $address, $age_is_exact, $age_value, $age_unit, IncidentNumber, responseDatetime, address, division, batalion, EMD
Events metadata
This metadata is related to events that happened during the call. In the export file, each row is an event and they will be listed chronologically per each case. As an example:
The column header with a $ are metadata originated in Corti, while the headers without it are custom metadata imported from external sources (i.e. CAD)
Please find here an example list of all the events endpoints (column headers)
- Events endpoints: $id,$case_id, $objective_name, $label_name, $name, $text, $datetime, dispatcherInit, changedTo, Enroute, OnScene, radioName, Cleared, changedFrom