Rendered live from /api/openapi.json (v1.0.0) — the same OpenAPI 3.1 document SDK generation runs against. Every /v1 response uses the { ok, data } / { ok, error } envelope.
Loading interactive explorer…
/v1/dashboarddashboard/v1/unitsinventory/v1/unitsinventory/v1/units/{unitId}inventory/v1/units/{unitId}inventory/v1/units/{unitId}inventory/v1/leadscrm/v1/leadscrm/v1/leads/{leadId}crm/v1/leads/{leadId}crm/v1/leads/{leadId}crm/v1/contactscrm/v1/contacts/{contactId}crm/v1/dealsdeals/v1/dealsdeals/v1/deals/{dealId}deals/v1/deals/{dealId}deals/v1/serviceservice/v1/serviceservice/v1/service/{roId}service/v1/callscalls/v1/rooftopsrooftops/v1/reportsreports/healthzno auth/demo/unitsno authEndpoints marked "Planned — Q3 2026" on /developers are intentionally absent here: this spec documents only what returns 200 today.
openapi-generator turns this document into a typed client in 20+ languages. Our own TypeScript SDK is generated the same way — see /sdks.
curl -o openapi.json https://autodealerpro.io/api/openapi.json
npx @openapitools/openapi-generator-cli generate \
-i openapi.json -g typescript-fetch -o ./adp-client