Skip to content

Integration Standards

Repo: savvydealer-adam/integration-standards · Path: C:/Users/adam/integration-standards · Owner: Adam Status: Active dev · % Done: 60 · Last commit: 2026-04-01 Deployed: N/A (docs-only repo)

What it is

Canonical contract definitions for how SavvyDealer tools talk to each other via webhooks: event naming, envelope format, auth, retries, endpoint conventions.

Why it exists

Every internal tool had been inventing its own webhook shape, auth scheme, and retry policy. Integration Standards is the single source of truth so CRM, DealerPulse, Contracts, Image Collage Pro, Dealer Tracker, and Lease Scraper all speak the same protocol.

How it works

Markdown docs + locked conventions. - Event name format: {service}.{entity}.{action} (e.g. crm.dealership.stage_changed) - Envelope: {event, timestamp, source, version, data} - Auth: shared secret in x-webhook-secret header, per-integration-pair - Endpoint pattern: POST /api/webhooks/{source} - Dispatch rules: fire-and-forget, 5s timeout, 3 retries with exponential backoff (1s/5s/25s), log every attempt

What's done

  • Event naming convention locked
  • Registered events table for CRM + DealerPulse
  • Envelope format + required fields
  • Auth + secret management patterns
  • Dispatch/retry rules

What's next

  • Add events for Contracts, Image Collage Pro, Dealer Tracker, Lease Scraper (prefixes reserved, events TBD)
  • Add signature-verification (HMAC) option as stronger auth mode
  • Add dead-letter handling pattern

Where the code lives

  • C:/Users/adam/integration-standards/README.md (entire spec)
  • No code — reference doc

Integrations

  • Consumed by: AI CRM, DealerPulse, Contracts, Image Collage Pro, Dealer Tracker, Lease Scraper
  • Every service implementing webhooks MUST conform

Don't rebuild this — extend it

Before adding a new webhook or cross-service event, update this repo's event table and envelope docs, then implement against the standard.