Everlance API integration (trip log, expense & IRS export)

Deliverables checklist

• OpenAPI / Swagger specification for trips, expenses, exports, and team endpoints
• Authorization flow report (login, session refresh, token rotation, MFA handling)
• Runnable source for trip-pull and expense-pull APIs (Python / Node.js)
• Scheduled export worker (cron / queue) with retry, dedupe, and idempotency keys
• Adapter layer: native JSON ↔ CSV ↔ MileIQ-compatible CSV ↔ QuickBooks IIF
• Automated tests, replay fixtures, and live-fire integration test plan
• Compliance guidance (IRS audit trail, CCPA/CPRA, GLBA Safeguards Rule)

Technical implementation

Three short examples show the auth handshake, a trip statement pull, and a webhook notification — these are pseudo-code and reflect typical patterns; concrete endpoint paths are tailored to each engagement.

// 1) Authorization handshake
POST /api/v1/everlance/auth/login
Content-Type: application/json

{
  "email": "driver@example.com",
  "password": "",
  "device_id": "of-lab-worker-01"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8f9...",
  "expires_in": 3600,
  "user_id": "usr_2x4...",
  "plan": "professional"
}

// 2) Pull classified trip log for a date range
POST /api/v1/everlance/trips/list
Authorization: Bearer <ACCESS_TOKEN>

{
  "from": "2026-04-01",
  "to":   "2026-04-30",
  "classification": ["work"],
  "business_line": ["doordash", "uber"],
  "page": 1,
  "page_size": 200
}

200 OK
{
  "items": [
    {
      "trip_id": "trp_a1b2",
      "started_at": "2026-04-12T08:14:03-07:00",
      "ended_at":   "2026-04-12T08:41:55-07:00",
      "distance_mi": 14.62,
      "start": {"lat": 37.7849, "lng": -122.4094},
      "end":   {"lat": 37.7212, "lng": -122.4769},
      "classification": "work",
      "business_line": "doordash",
      "vehicle_id": "veh_civic_2019",
      "deductible_usd": 10.59
    }
  ],
  "page": 1, "total": 86, "next": "/api/v1/everlance/trips/list?cursor=..."
}

// 3) Webhook: new bank-linked expense captured
POST https://your-stack.example.com/hooks/everlance
X-OFLab-Signature: t=1715300000,v1=9c3f...

{
  "event": "expense.created",
  "occurred_at": "2026-05-08T15:02:11Z",
  "data": {
    "expense_id": "exp_77ab",
    "amount_usd": 38.42,
    "merchant": "Shell #2148",
    "category": "fuel",
    "receipt_url": "https://files.everlance/.../r_77ab.jpg",
    "linked_account": "card_visa_4242",
    "notes": "Friday delivery shift"
  }
}

// Recommended: verify HMAC signature, store idempotency key, ACK 2xx fast,
// then push into your accounting queue.

Typical integration scenarios

1. Multi-gig driver reimbursement. A logistics aggregator paying its 1099 fleet pulls each driver's classified trips nightly, multiplies by the current IRS standard rate, and stages a reimbursement file for ACH the next morning. Trip API + per-job tag drive the cost allocation; the GLBA Safeguards Rule shapes where bank-linked card data may live in the pipeline.

2. Real-estate brokerage accounting sync. A brokerage with 60 agents pipes each agent's monthly mileage and expense exports into QuickBooks Online via the existing Everlance ↔ QuickBooks sync, then re-routes copies into the brokerage's own BI warehouse. The integration layer normalizes business-line tags so the brokerage's chart of accounts matches what individual agents already use in-app.

3. Tax software pre-fill. A consumer tax product wants to pre-populate Schedule C, line 9 with deductible miles before the user files. We pull the YTD totals endpoint, validate them against IRS audit-trail requirements (date, distance, purpose, route), and post them as a pre-fill payload to the tax product's onboarding flow. Pairs naturally with Everlance's 2024-2025 Column Tax in-app filing capability.

4. Field-services dispatch reconciliation. A HVAC or pest-control dispatcher matches dispatched jobs (work-order ID) against the technician's actual trip log to validate route compliance and time on site. We use Everlance trip start/end geocodes plus the work-order address from the dispatch system to compute on-site dwell time and travel cost per job.

5. Audit defense / IRS examination support. A driver who has been picked for examination needs a contemporaneous mileage log. We export the IRS-ready PDF report for the requested tax year, include the bank-linked expense receipts inline, and produce a single packet keyed by trip ID and transaction ID so an auditor can cross-walk the log without re-asking the taxpayer.

Compliance & privacy

Mileage logs and bank-linked expenses are squarely inside several US regulatory perimeters. Engagements scope these explicitly:

• IRS substantiation — exports include the four substantiation fields the Schedule C instructions expect: date, distance, business purpose, and a way to verify the route.
• GLBA Safeguards Rule — applies when card/account data flows through the integration host; access controls, encryption in transit/at rest, and incident response are baseline.
• CCPA / CPRA — Everlance's California user base falls under state privacy law; we follow data-minimization, purpose limitation, and a clear deletion path.
• GDPR / UK GDPR — applies if the integration handles drivers in the EEA or UK; lawful basis, retention, and DSAR are addressed in the runbook.
• Authorized access only — we never bypass MFA or scrape against the account owner's wishes; integrations require an explicit authorization record.

Data flow / architecture

A typical pipeline is short and inspectable end-to-end:

1. Everlance app / authorized session — source of trips and expenses.
2. OpenFinance Lab ingestion worker — auth + retry + dedupe; writes raw JSON to object storage.
3. Normalization layer — maps to a canonical schema (trip, expense, summary).
4. Outbound adapters — QuickBooks Online, NetSuite, Xero, BI warehouse (Postgres / BigQuery), or your REST endpoint.
5. Audit log + access control — every read and every export is logged with actor, scope, and timestamp.

About our studio

We are an independent technical studio focused on App interface integration and authorized API integration for global clients. Our engineers have shipped protocol-level work for banking, payments, gig-economy, and accounting platforms. For mileage and expense apps specifically, we know how IRS audit-trail expectations, GLBA Safeguards, and modern OpenFinance patterns interact with consumer apps like Everlance.

• Protocol analysis, authorization flow reverse engineering, and SDK design
• Custom Python / Node.js / Go API wrappers, plus QuickBooks / Xero / NetSuite adapters
• Full pipeline: analysis → build → validation → compliance hand-off
• Source code delivery from $300 — receive runnable API source code and full documentation; pay after delivery upon satisfaction.
• Pay-per-call API billing — access our hosted API and pay only per call, no upfront cost; ideal for teams that prefer usage-based pricing.

Contact

Send us the target app, the data you need, and the destination system (accounting, payroll, BI, tax product). We respond with a scope, price, and timeline.

Contact page

Engagement workflow

1. Scope confirmation: data types (trips, expenses, exports), destination system, multi-user vs. single-user.
2. Authorization plan: where credentials live, how MFA is handled, NDA execution.
3. Protocol analysis and API design (2–5 business days).
4. Build and internal validation against a sandbox account (3–8 business days).
5. Docs, samples, and replay test cases (1–2 business days).
6. Typical first delivery: 5–15 business days; multi-tenant team rollouts can extend timelines.

FAQ

Does Everlance offer a public developer API?

What data can be extracted from Everlance for accounting or payroll?

How long does a typical Everlance integration take?

Is this compliant with US tax and privacy rules?