Auto-dealer integration · technical preview

Inventory in. Settlement out.

For dealer IT leads, F&I directors, and developers integrating qardon.com into the lot operations stack. Three integration paths: DMS sync (DealerSocket / Reynolds & Reynolds / CDK Global), CSV bulk-upload, and direct REST API. The full production OpenAPI 3.1 spec is not published yet. This page is a forward-looking technical preview for scoping the integration ahead of time.

DMS integration partners

Native sync with the platforms you already run.

Real-time inventory sync. Sub-15-minute latency. Approval webhooks back to your DMS. No double-entry.

▣

DealerSocket launch

Native bidirectional sync. Inventory feed from DealerSocket → qardon.com listings. Approval + settlement events written back to DealerSocket deal jacket.

▤

Reynolds & Reynolds launch

R&R ERA-IGNITE integration. Inventory + customer data sync via R&R Connect APIs. Compliance with R&R partner certification program.

▥

CDK Global launch

CDK Drive integration via Fortellis API marketplace. Real-time inventory + deal-jacket sync. Approved CDK Partner Program vendor.

{ }

Direct REST API v1

For independent dealers or custom integrations. OAuth 2.0 + HMAC signing. Full inventory, transaction, settlement, and dispute endpoints. Sandbox + production environments.

▦

CSV bulk-upload v1

Dealer dashboard accepts CSV files for one-shot inventory upload or scheduled re-sync. Standard format documented below. No-code option for small lots.

▧

VinSolutions · Dealertrack v1.1

Secondary-tier DMS integrations targeted for v1.1. Customers on these platforms can use the direct REST API or CSV upload at launch and migrate to native sync when v1.1 ships.

CSV bulk-upload spec

One file. Hundreds of vehicles. Live in minutes.

Headers required (UTF-8, comma-separated). Sample shown:

# inventory.csv — qardon.com auto-dealer bulk-upload format v1
vin,year,make,model,trim,mileage,asking_price,condition,exterior_color,interior_color,transmission,drivetrain,fuel_type,photo_urls,description,location_id

"1HGBH41JXMN109186",2023,"Honda","Civic","EX",18420,23900,"used","Silver","Black","CVT","FWD","Gasoline","https://cdn.example.com/lot/civic-1.jpg|https://cdn.example.com/lot/civic-2.jpg","One owner. Clean Carfax. Service records included.","lot-main"

"5YJ3E1EA8MF123456",2024,"Tesla","Model 3","Long Range",8120,39500,"used","White","Black","Auto","AWD","Electric","https://cdn.example.com/lot/m3-1.jpg","Certified pre-owned. Full self-driving included.","lot-main"

Required fields: vin, year, make, model, mileage, asking_price, condition (one of: new, used, certified). Photo URLs are pipe-separated for multiple images. VIN-level deduplication is enforced — same VIN cannot be listed by multiple dealers.

REST API

Auto-dealer endpoints overview.

OAuth 2.0 client credentials. HMAC-signed payloads. Idempotency keys on every mutating request. Sandbox + production environments.

Method Endpoint Purpose Status
POST /api/v1/dealer/inventory Create or update a single vehicle listing. Returns listing ID. v1
POST /api/v1/dealer/inventory/bulk Bulk-upload inventory (CSV multipart or JSON array). Returns per-row success/failure. v1
GET /api/v1/dealer/inventory List your active inventory with filters (status, aging, category, asking-price range). v1
DELETE /api/v1/dealer/inventory/:vin Withdraw a listing. Pending-sale items locked until transaction resolves. v1
POST /api/v1/dealer/transactions Create a transaction from a buyer application. Triggers creditworthiness check + approval flow. v1
GET /api/v1/dealer/transactions/:id Retrieve transaction status, approval result, installment schedule, settlement record. v1
GET /api/v1/dealer/settlements Settlement reports with date-range filters. Per-transaction details + reconciliation. v1
GET /api/v1/dealer/aging Inventory aging report — vehicles over 60 days flagged with suggested actions. v1
POST /api/v1/dealer/tradein/valuation Trade-in valuation via KBB + Black Book APIs. Returns instant offer for buyer. v1
GET /api/v1/dealer/buyers/prequalified List qardon.com pre-qualified buyers (with their consent) browsing your inventory. v1.1
Sample request — inventory POST

List a single vehicle.

curl -X POST https://api.qardon.com/api/v1/dealer/inventory \
  -H "Authorization: Bearer ${QARDON_API_KEY}" \
  -H "X-Qardon-Signature: ${HMAC_SIGNATURE}" \
  -H "X-Qardon-Idempotency-Key: ${UUID}" \
  -H "Content-Type: application/json" \
  -d '{
    "dealer_id": "dealer_abc123",
    "vin": "1HGBH41JXMN109186",
    "year": 2023,
    "make": "Honda",
    "model": "Civic",
    "trim": "EX",
    "mileage": 18420,
    "asking_price_cents": 2390000,
    "condition": "used",
    "exterior_color": "Silver",
    "interior_color": "Black",
    "transmission": "CVT",
    "drivetrain": "FWD",
    "fuel_type": "gasoline",
    "photo_urls": [
      "https://cdn.example.com/lot/civic-1.jpg",
      "https://cdn.example.com/lot/civic-2.jpg"
    ],
    "description": "One owner. Clean Carfax.",
    "term_options_months": [24, 36, 48, 60, 72],
    "location_id": "lot-main"
  }'

Response includes the listing ID and the live qardon.com listing URL where buyers can apply. VIN-level dedup enforced — duplicates surfaced to qardon.com partnerships team.

Sample request — transaction create

Approve a buyer in seconds.

curl -X POST https://api.qardon.com/api/v1/dealer/transactions \
  -H "Authorization: Bearer ${QARDON_API_KEY}" \
  -H "X-Qardon-Signature: ${HMAC_SIGNATURE}" \
  -H "X-Qardon-Idempotency-Key: ${UUID}" \
  -H "Content-Type: application/json" \
  -d '{
    "dealer_id": "dealer_abc123",
    "listing_id": "lst_civic_xyz",
    "buyer": {
      "email": "[email protected]",
      "first_name": "Jane",
      "last_name": "Doe",
      "phone": "+15551234567"
    },
    "selected_term_months": 48,
    "down_payment_cents": 200000,
    "trade_in_offer_id": "tradein_def456",
    "webhook_url": "https://dealership.example/qardon-webhook"
  }'

Response: hosted checkout URL for the buyer to e-sign + payment-method capture. Final approval webhook fires to your endpoint with installment schedule and settlement date. Settlement initiated T+2 via ACH or wire.

Sample request — settlement GET

Daily settlement reports.

curl -X GET "https://api.qardon.com/api/v1/dealer/settlements?start=2026-05-01&end=2026-05-14" \
  -H "Authorization: Bearer ${QARDON_API_KEY}" \
  -H "X-Qardon-Signature: ${HMAC_SIGNATURE}"

Returns per-transaction settlement records: transaction ID, asking price, the amount paid to you (the full price: qardon.com deducts nothing), ACH trace number. Reconciliation file downloadable as CSV or JSON.

Architecture

From inventory upload to settlement.

  1. You upload inventory. CSV bulk-upload, VIN-by-VIN dashboard entry, or DMS feed sync. VIN-level dedup runs at write time.
  2. Listings go live on qardon.com. Buyers browse the marketplace; your dealership name and lot location are visible. Pre-qualified buyers see the "qardon-approved" badge filter.
  3. Buyer applies on a specific vehicle. His email and phone are confirmed in seconds. The credit-decisioning surface, and the adverse-action notice that would go with it, are specified and not built — nothing sends one today.
  4. Approval webhook fires to your endpoint. Transaction ID, approved installment schedule, down-payment requirement, trade-in valuation if applicable.
  5. Buyer e-signs the agreement. Payment method captured (debit / ACH / Apple Pay). First payment authorized.
  6. Title-transfer orchestration starts. Per-state: some allow online, some require in-person. On the dealer-carried sale that is live today, you retain title until the buyer fully pays. On the cash-purchase route, which is not built, title would transfer to the buyer at close with qardon.org holding a security interest until paid.
  7. Settlement initiated. You receive the asking price in full — qardon.com deducts nothing, on any sale.
  8. Your customer pays you directly. From his own bank to yours, by Zelle or Bill Pay; qardon.com never holds or collects the money. No late charges, and a buyer in hardship is offered help, never a penalty.
  9. Reconciliation reports delivered. Daily settlement file + monthly statement + on-demand API exports + DMS deal-jacket write-back.
Developer waitlist

Get the OpenAPI spec + sandbox access.

The documentation is not published yet. When the sandbox opens you will receive: the full OpenAPI 3.1 spec, DMS integration guides per platform, CSV upload templates, sandbox credentials, and a technical support contact during integration. This form records your interest; nothing opens from it today.

Routed to support@qardon.com, which is a live mailbox. Your request is recorded; no reply date is promised, and the sandbox is not open yet.