Civesto is a Touman Studio product.

etkaahmet@toumanstudio.comTürkçe

Discuss a pilot

Bring the case into your existing system.

Civesto provides a documented REST API, webhooks and exports in DATEX II, GeoJSON, CSV, XLSX and PDF.

DATEX II export is for road reports and is a generic v3.5 test publication. National profiles and real publication are not enabled.

Connect to your existing systems

An export adapter is not a completed integration: the receiving organisation validates the format and the permitted fields.

Read the API reference

Review the existing API reference alongside the read-only authority console.

Cases can be exported as DATEX II, GeoJSON, CSV, XLSX or PDF. The system provides a documented REST API and webhooks.
Export and delivery
CSV
Excel workbook
PDF
DATEX II v3.5
GeoJSON

DATEX II export is for road reports and is a generic v3.5 test publication. National profiles and real publication are not enabled.

For road reports, a Common Alerting Protocol 1.2 envelope of the routing decision can be downloaded on request. It is an interoperable format.

Read the interface

The API takes one header, an API key that carries the scopes it needs and nothing more. A key can never create another key with more than it holds.

A key sees only the reports of its authority's area. An id outside it answers as not found.

Evidence media is served only through the key, never by file name.

The authority can read its own audit log through the API: time, action, result, origin address and duration for every call made with its keys.

Verify the delivery

The API reference describes event deliveries signed with HMAC-SHA256. The receiving system recomputes the signature from the raw request body and compares it with the delivery header.

Webhooks announce new reports and recorded outcomes. Failed deliveries are retried on a lengthening schedule and every attempt is in a delivery log.

This checks a webhook delivery. It does not establish that a reported event occurred.

The receiving case-management system stays the system of record; Civesto pushes events to it.

Check file integrity

The upload handler computes a SHA-256 digest from the received file bytes before analysis.

A matching digest checks the file bytes. It does not prove that an event occurred.

Each file is digested as it arrives, before any processing. The stored file is not re-encoded, so the digest stands for the original.

A file is accepted for what it is, not for its name: the type is read from the opening bytes of the file, and a file that fails the check is not stored.

Reports that carry media are signed and linked to the previous record in a hash chain; if the seal cannot be written, the report is still recorded and the failure is logged. The time in the record is the server's clock.

Comparing a file with a recorded digest checks whether those bytes match. It does not establish that the recorded event is true.

SHA-256 of this file

91448bdd92be3e61135d21e31b18d9df488f49740a1d13562bc7546f3ebef2f5
Illustration; no real case is shown.

A matching digest checks the file bytes. It does not prove that an event occurred.

Check the file yourself

This separate test file was prepared to check file integrity. It was not submitted to the live service.

Files up to 10 MB (10,000,000 bytes). The file stays in this tab; nothing is uploaded.

Only an in-memory copy changes. Your original file is untouched.

Metadata is read only from JPEG headers, identified by their bytes, not the filename. Other files are hashed only.

HEIC metadata is not read by this tool. The SHA-256 digest covers the file bytes.

These are header observations, not image decoding or authenticity validation. A missing marker or metadata is not evidence of manipulation.

Download the test file

shasum -a 256 integrity-test.txt
7c150c8f4f1d138cd313e8ca47609a4faf864a8c6459019a98cc5d7ef78e63a1

Plan the connection

A bounded pilot

Discuss which reports enter the workflow, which formats the receiving system expects and what the pilot will measure.

Discuss a pilot

Discuss your authority’s workflow.

etkaahmet@toumanstudio.com