Road survey data validation, as an API
We're opening the engine that powers RoadSense to other engineering teams. Submit raw road-condition data — get back validation feedback, TMH 18-structured exports for your clients’ review, and an audit trail of what was checked. Today the public API accepts file uploads and lists projects; the rest of this page is the plan.
Empower the industry, not just our portal
Every road authority, consultant, and instrument vendor in South Africa needs the same things from their data. The pavement engineer needs roughness interpreted with its measurement context. The asset manager needs TMH 18 combined instrument data (CID) exports. The visual-assessment team needs COTO forms. And every one of them is implementing it from scratch.
We've spent years building this engine for our own users. We process real survey data for our own projects, and we've already met the edge cases — unit ambiguities between instrument formats, direction and chainage reconciliation, multi-take consolidation and the Horak (2008) deflection-bowl parameters. Rebuilding it costs every team months of work and ships every team a slightly different answer to the same regulatory question.
We're going to open it. Call our API with your raw survey data. Get back the same validation, the same exports, and the same artefacts our own users get — without rebuilding the toolchain. Build your own portal, your own apps, your own workflow on top of an engine that already speaks the standards.
Six surfaces. One contract.
Each surface speaks to the same REST API, authenticated with per-organisation API keys. Use one or use them all — they share the same project model, the same standards engine, and the same audit log.
Validation API (planned)
Submit raw IRI, FWD, MPD, video, or shapefiles. Receive per-row diagnostics: threshold violations, unit errors, missing fields, GPS outliers, broken chainages — each issue linked to the applicable validation rule.
Structured exports
TMH 18 CID and FWD files, TMH 13 IRI CSV and COTO assessment workbooks — the same exports our own users download. Agree the receiving authority’s version before submission.
Spec-pinned schemas (planned)
Pin a project to the specification revision your client has agreed. When a revision changes, see what changed and re-emit. No silent drift between submissions.
Event webhooks (planned)
Subscribe to lifecycle events — project ingested, validation complete, export ready, threshold crossed — and push them straight into your own systems. No polling, no glue code.
Client libraries
A Python client for scripted uploads is available today. TypeScript and .NET clients are planned. Every call is scoped to your organisation and logged.
Multi-tenant by default
Use it as a private back-end for your own platform, or as a shared service across multiple client orgs. The same role-based privileges and per-org audit log that power our own portal.
If you're shipping pavement data, you're in scope
Engineering platforms
Building your own road-asset platform? Use our parsers and TMH 18 export builders as a back-end service instead of writing your own.
Instrument vendors
Ship your profilometer or FWD with a "submit to RoadSense" button. Customers get structured exports for project review.
Road authorities
Validate every contractor submission against the same engine you trust internally. One source of truth across your panel of providers.
Early access is open
The API is being designed with the teams who will use it. Tell us about your platform and the data you ship, and we'll add you to the early-access list.