DealerMAX Developers
PartnerMAX Enterprise API
PartnerMAX is the selected-partner enterprise API. It is separate from the Dealer Public API because it covers authenticated multi-dealer workflows: dealer-reference provisioning, dealer-scoped used stock, image upload, accessories, lifecycle management, and per-dealer NLT configuration.
When PartnerMAX fits
- DMS vendors and automotive SaaS platforms onboarding dealer networks.
- Enterprise partners that need write-side workflows.
- Integrations that require contract, billing, and support review.
Onboarding paths
| Standard Trial Path | Self-service company verification through /signup, 15-day live trial, limited enterprise access, no custom SLA, and no contractual commitments until conversion. |
|---|---|
| Enterprise Onboarding Path | Commercial agreement, support-managed credentials, sandbox and production enablement, procurement, DPA/security review, custom quotas, and contracted support terms where required. |
Sandbox and production
Sandbox and production share the same host
(api.dealermax.app). The environment is chosen by the API key
prefix: pmk_live_* = production,
pmk_sand_*/pmk_test_* = sandbox. There is no
separate sandbox host — switch the API key only, not the base URL.
Current SDK contract
| Dealer reference | client.dealers.create(...) maps to POST /api/partner/dealers. Partners send an opaque external_dealer_id; DealerMAX stores the registry link and hidden technical tenant only. |
|---|---|
| Vehicle stock | client.dealers.vehicles.* maps to /v1/dealers/{dealer_id}/vehicles.... There is no global vehicle listing; every call names one registered dealer. |
| Images | client.dealers.vehicles.images.create(...) uploads multipart file data. Python passes a file-like object; Node uses toFile(..., { type: "image/jpeg" }). |
| Accessories | Optionals, packages, and equipment are ID-based. Read /accessories/catalog first, then replace selections with IDs returned by the catalog. |
| NLT | client.dealers.nlt_settings.* and client.dealers.nlt.offers.* are dealer-aware and apply each dealer's markup/down-payment settings. |
| Cache posture | Authenticated PartnerMAX reads are no-store and vary by Authorization / X-Api-Key. |
Resources
| Enterprise docs | https://developers.dealermax.app/docs |
|---|---|
| Contract access | Shared during onboarding for approved enterprise integrations. |
| Technical PDF | https://developers.dealermax.app/partner-brief |
| Enterprise SDKs | Existing typed SDKs: PyPI partnermax / partnermax-python and npm partnermax / partnermax-node. |
| Security | https://developers.dealermax.app/security |
If you only need a dealer's own stock/offers for a custom frontend, use the Dealer Public API instead.