Just: Affordable Car Insurance — API integration & telematics OpenData

1. Quote & onboarding API

Mirror the 60-second sign-up flow: vehicle lookup by VIN or license plate, driver KYC fields, MVD/DMV cross-check, and the instant quote callback. Use it to pre-fill aggregator funnels or to embed Just quotes inside an auto-loan checkout.

2. Odometer photo capture & OCR

An endpoint that accepts dashboard photos, returns the parsed odometer reading, confidence score and a reusable photo asset ID. Powers reconciliation of declared miles against the telematics ledger and supports dispute workflows.

3. Premium & balance statement API

Daily fixed-charge plus per-mile usage broken down by trip and date range. Filterable export to JSON, CSV or PDF, mapped to QuickBooks / Xero / NetSuite chart-of-accounts so finance teams can reconcile vehicle expenses without screen-scraping.

4. ScoreSafe telematics stream

Driving events (hard brake, harsh cornering, over-speed, distraction) returned as time-series records with GPS-snapped polylines. Feeds usage-based insurance research, fleet manager dashboards and gamified driver-coaching apps.

5. Proof-of-insurance & ID card

On-demand digital insurance certificate that meets Arizona MVD and Nevada DMV requirements. Returned as a signed PDF plus structured fields (policy number, NAIC code, effective dates) so it can be auto-attached to vehicle registration apps.

6. Webhooks & lifecycle events

Subscribe to policy.activated, balance.low, trip.recorded, scoresafe.updated, and renewal.due. Webhook signatures use HMAC-SHA256 with replay protection so partner backends can react in real time.

Scenario A — Rideshare driver expense reconciliation

An Arizona Uber/Lyft driver wants every rideshare-related dollar deducted at tax time. We pull the per-mile billing breakdown plus daily base charges from the Just premium statement API, tag each line with the trip's GPS polyline, and post the result to QuickBooks Self-Employed via its journal-entry endpoint. Mapping: Just /v1/billing/usage → QBO journal_entry.line_items.

Scenario B — Fleet safety dashboard

A Phoenix-based home-services franchise insures 12 vans through Just. ScoreSafe events are streamed via webhook to an internal Grafana board that flags hard-braking clusters by route. Mapping: scoresafe.event webhook → Kafka topic fleet.driving_events → Grafana Tempo for trace-style replay of risky trips.

Scenario C — Auto loan & lease compliance

A credit union in Las Vegas requires continuous proof of full-coverage on financed vehicles. Our integration polls the policy declarations endpoint nightly and pushes a signed JSON document to the loan origination system; if coverage drops or lapses, a policy.coverage_changed event triggers a force-placed insurance workflow.

Scenario D — UBI research dataset

An academic actuarial group studies pay-per-mile claim frequency vs ScoreSafe percentile. We deliver a de-identified bulk export (driver_id hashed, geos coarsened to H3 r=7) covering 12 months of trips and events, with a documented schema aligning to NAIC's UBI study series so the dataset is regulator-friendly.

Scenario E — Embedded broker quote widget

An independent broker site offers Arizona drivers a side-by-side quote that includes Just alongside national carriers. The integration calls the quote endpoint with VIN, ZIP and predicted annual mileage, returns the binding URL, and tracks conversion via a webhook on policy.activated for commission settlement.

Deliverables checklist

• OpenAPI 3.1 specification covering quote, policy, mileage, ScoreSafe, billing and webhook endpoints
• Protocol analysis report: TLS pinning, OAuth2 / token refresh chain, request signing, anti-replay nonces
• Runnable reference SDKs in Python and Node.js, with retry/backoff and idempotency keys
• Postman collection plus contract tests (Pact) and a sandbox harness with seeded fixtures
• Compliance brief: NAIC UBI guidance, Arizona Title 20 insurance code, Nevada NRS Chapter 690B alignment notes, GLBA + CCPA-style data handling

API example: authentication

POST /api/v1/just/auth/token
Content-Type: application/json

{
  "grant_type": "password",
  "username": "driver@example.com",
  "password": "<hashed>",
  "device_fingerprint": "az-pixel-9-3f2c"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8d2c...",
  "expires_in": 3600,
  "scope": "policy mileage scoresafe billing"
}

API example: mileage ledger query

GET /api/v1/just/mileage?from=2026-03-01&to=2026-03-31
Authorization: Bearer <ACCESS_TOKEN>
X-Idempotency-Key: 9b1f-march-pull

200 OK
{
  "policy_id": "JI-AZ-77821",
  "vehicle": {"vin":"1HGCM82633A...","state":"AZ"},
  "period": {"from":"2026-03-01","to":"2026-03-31"},
  "trips": [
    {"trip_id":"t_001","start":"2026-03-02T14:11Z",
     "end":"2026-03-02T14:38Z","miles":11.4,
     "score_safe":{"brake":2,"corner":0,"speed":1}}
  ],
  "billing": {"base_days":31,"miles":312.7,
              "rate_per_mile_cents":6.4,
              "amount_due_cents":2899}
}

API example: ScoreSafe event webhook

POST https://your-app/webhooks/just
X-Just-Signature: t=1714080000,v1=8c2f...
Content-Type: application/json

{
  "event": "scoresafe.updated",
  "policy_id": "JI-NV-30418",
  "window": "rolling_30d",
  "score": 87,
  "components": {
    "hard_brake_per_100mi": 1.2,
    "harsh_cornering_per_100mi": 0.4,
    "over_speed_minutes": 6,
    "phone_distraction_minutes": 2
  },
  "recommendation": "discount_tier_2"
}

Regulatory frame

Auto insurance in the United States is regulated state-by-state. For Just: Affordable Car Insurance, that means alignment with Arizona Department of Insurance and Financial Institutions (DIFI) rate filings under Arizona Revised Statutes Title 20, and Nevada Division of Insurance rules under NRS Chapter 690B. Telematics data handling follows NAIC's UBI guidance, with FTC 2025 enforcement underscoring opt-in consent for driving data sharing.

Data minimization & consent

Every integration we ship enforces explicit driver consent capture, scoped OAuth tokens, and a documented retention window. GLBA-style safeguards apply to non-public personal information, and California-resident records are handled with CCPA/CPRA deletion and access workflows. We log access for audit and pass redaction rules through our SDKs by default.

Security controls

TLS 1.3 with certificate pinning where applicable, HSTS, HMAC-SHA256 webhook signing with replay-window enforcement, secrets handled via cloud KMS, and rate-limited endpoints with anomaly detection. We also include incident-response runbooks aligned with NIST 800-61.

Metromile (now part of Lemonade Car)

One of the original pay-per-mile carriers in the U.S., acquired by Lemonade in 2022. Holds per-trip miles, OBD-II driving signals and policy ledgers — teams who use both Metromile and Just often need a unified mileage-export pipeline.

Mile Auto

Smartphone-only, photo-of-odometer pay-per-mile insurer. Mile Auto's data model overlaps closely with Just's odometer-photo flow, so cross-app reconciliation jobs frequently share the same OCR pipeline.

Allstate Milewise

Daily-rate plus per-mile auto insurance. Customers comparing usage-based programs often want a side-by-side dashboard pulling Milewise daily charges alongside Just's premium statements.

Nationwide SmartMiles

Pay-per-mile program available across roughly 40 states with a 250-mile daily cap. Brokers building national low-mileage comparison tools surface SmartMiles next to Just for non-AZ/NV drivers.

Lemonade Car

Mobile-first carrier running on Metromile rails, with strong API ergonomics. Useful as a reference architecture for clients designing their own Just-compatible OpenInsurance endpoints.

Root Insurance

Telematics-priced auto insurance built around a smartphone test-drive period. Like Just's ScoreSafe, Root scores braking, cornering and distraction — overlapping schemas for any driver-behavior aggregator.

State Farm Drive Safe & Save

Discount program rather than full UBI, but its trip-event records and renewal discount flag are commonly merged with Just data for fleet retention analysis.

GEICO DriveEasy

National telematics program. Aggregators that already pull DriveEasy event streams typically bolt on Just's ScoreSafe webhook for AZ/NV pay-per-mile customers.

Progressive Snapshot

Long-running telematics program with both plug-in and mobile variants. Comparable event taxonomy to ScoreSafe — a natural fit for shared driver-coaching dashboards.

Liberty Mutual RightTrack

Telematics-based discount program. Brokers writing across both Just and RightTrack need a single export schema to support unified renewal and discount-tier reporting.

About our studio

We are an independent technical studio focused on App interface integration and authorized API integration for fintech and insurtech. Our team has shipped production integrations for banking, payments, lending, brokerage and insurance apps across the U.S., Europe, India, Brazil and Southeast Asia, with hands-on experience in mobile reverse engineering, OAuth2 / OIDC flows, certificate pinning, anti-bot defenses and telematics SDKs.

• Insurtech: pay-per-mile, telematics, claims and policy admin integrations
• OpenData / OpenFinance / OpenBanking adapters and consent management
• Custom Python / Node.js / Go SDKs and contract test harnesses
• End-to-end pipeline: protocol analysis → build → validation → compliance
• Source code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost

Contact

For a quote on Just: Affordable Car Insurance integration — pay-per-mile billing exports, ScoreSafe telematics streams, policy declarations APIs, or a full OpenData adapter — open our contact page and share your target scope and any sandbox credentials.

Contact page

Typical kickoff: scope confirmation within 1 business day, signed NDA on request, and a dated quote within 2–3 business days.

Engagement workflow

1. Scope confirmation: which Just data (mileage, ScoreSafe, billing, claims) and target downstream system.
2. Protocol analysis & API design: 2–5 business days depending on auth complexity.
3. Build & internal validation against sandbox or shadow traffic: 3–8 business days.
4. Documentation, sample SDK, Postman collection and contract tests: 1–2 business days.
5. Typical first delivery: 5–15 business days; carrier or regulator approvals can extend timelines.

FAQ

Do you need my Just account credentials?

How long does delivery take?

Is this lawful?

Can I pay per call instead of upfront?