Introduction

This section provides an overview of how partners integrate with Dealerware APIs, including authentication, request flows, and supported integration patterns.

Whether you are building your first integration or expanding an existing partnership, Dealerware offers secure, scalable REST APIs that enable full fleet and mobility workflows. These APIs are designed to reduce operational friction, minimize screen-based workflows, and support real-time system-to-system communication.

The diagram above illustrates the end-to-end integration and authentication flow used by Dealerware, from credential exchange through API request validation.

Get your API keys

You must have received the Client ID and Client Secret from our team in order to use Dealerware's API.

NOTE: If you have not received these credentials, please contact our team: partnersupport@dealerware.com

  1. Follow the quick start guide for authorization instructions. Once you have received your Client ID & Client Secret, follow the instructions in the quickstart guide section. NOTE: In case of an authentication error, please get in touch with our Support Team.

  2. Keep your API keys secure. Your API keys allow access to our API, so please keep them secure! DO NOT SHARE your secret API keys on publicly accessible areas such as GitHub, client-side code, etc.

Integration Model

Dealerware integrations use a secure, token-based authentication model with flexible data exchange patterns.

Partners authenticate using machine-to-machine credentials, after which Dealerware issues short-lived, RS256-signed JWT access tokens via Auth0. All API requests are authorized using Bearer tokens and validated by Dealerware middleware before execution.

Once validated, Dealerware either:

Supported Integration Patterns