Skip to content
Traffica

Developers

A clean REST API for road and driving data

Everything in the dashboard is available through the API: GeoJSON for maps, CSV for analysis, and an upload contract for your devices. The full OpenAPI contract is shared with customers.

At a glance

Conventional on purpose

REST + JSON
GeoJSON for anything on a map, CSV exports for analysts, NDJSON for data-subject exports.
OAuth 2.0
Client-credentials access per organization, limited to the products you use.
OpenAPI contract
A committed contract that tests fail on if the code drifts from it.
Problem details
Errors follow RFC 9457, with machine-readable codes where a client needs to react.
Predictable limits
Time ranges and result sizes are bounded by role, and large results are paginated.
Honest metadata
Every V2X response says it is a probe sample and carries the OpenStreetMap attribution.

How access works

From credentials to data in three steps

Field names and details follow the API reference you receive with your credentials.

  1. 1Get credentialsYour organization’s admin creates an API client in the dashboard and chooses which products it can use.
  2. 2Request a tokenExchange the client’s credentials for a short-lived access token, using standard OAuth 2.0.
  3. 3Call the APISend the token with each HTTPS request. Responses come back as GeoJSON, CSV or JSON.
Example response: segment speeds (one feature)
{
  "type": "FeatureCollection",
  "metadata": {
    "dataKind": "PROBE_SAMPLE",
    "attribution": "© OpenStreetMap contributors",
    "truncated": false
  },
  "features": [
    {
      "type": "Feature",
      "geometry": { "type": "LineString", "coordinates": [[-73.9877, 40.7536], [-73.9866, 40.7541]] },
      "properties": {
        "bucketStart": "2026-10-12T16:15:00Z",
        "osmWayId": 46338190,
        "direction": "FORWARD",
        "samples": 41,
        "vehicles": 9,
        "meanSpeedMps": 4.1,
        "medianSpeedMps": 3.8,
        "p85SpeedMps": 6.2,
        "speedLimitMps": 11.18
      }
    }
  ]
}

Ingest

Uploads that tell you what happened to every record

Batches never fail because of one bad record. The answer summarizes the batch and lists every record that wasn’t simply stored, with the reason.

  • From your backend, in batches.
  • From devices directly, each authenticated with its own key.
  • Safe to retry: identical records are recognized and stored only once.

See a full upload body on the fleets page.

Upload response (simplified)
HTTP/1.1 200 OK

{
  "summary": { "stored": 997, "duplicate": 2, "sampledOut": 0, "rejected": 1 },
  "results": [
    { "deviceRef": "van-0142", "seq": 18240, "status": "DUPLICATE" },
    { "deviceRef": "van-0177", "seq": 9021, "status": "REJECTED", "reason": "NO_CONSENT" }
  ]
}

Capabilities

The API by product

Everything in the dashboard is available through the API. What each client can reach depends on your organization’s roles and entitlements; the full reference comes with your credentials.

  • Traffic

    Segment speeds for every road segment and direction in your area.

    • Mean, median and 85th-percentile speed per 15 minutes
    • Sample and vehicle counts, with the posted limit
    • GeoJSON for maps, CSV for analysis
  • Safety events

    Where hard braking and other safety events concentrate.

    • Events reported by vehicles or detected from motion
    • Hot spots per segment and per kilometre
    • Any time range your role allows
  • Intersections

    Signal performance and lane-level maps for your intersections.

    • Arrivals on green, platoon ratio, stops and delay
    • Red-light-running candidates as aggregate counts
    • Lane maps and signal broadcast health over time
  • Trips & mobility

    Your organization’s own trips, journeys and travel patterns.

    • Trips and journeys, with endpoints protected where required
    • Origin–destination flows
    • Daily usage per vehicle or driver
  • Driving scores

    Explainable scores for drivers and vehicles.

    • Every factor, its weight and the points it cost
    • Weights and minimum distance set by your organization
    • Scores over periods of up to a year
  • Ingest

    Bring your own phone and telematics data.

    • Batch uploads from your backend
    • Direct uploads from enrolled devices
    • A result for every record, and safe retries
  • Consent & privacy

    The tools to run identified data responsibly.

    • Consent records, with revocation that takes effect immediately
    • Driver invitations by code, link or email
    • Data-subject access and deletion
  • Organization

    Administration for your team and integrations.

    • Members and roles
    • API credentials for your systems
    • Retention settings and a full audit trail

Build on Traffica

Get the full OpenAPI contract, credentials for your organization and a walkthrough with our engineers when you get started.