Welcome


Welcome to DCP!
Welcome to the latest edition of our API documentation!
The Powersports Data Standards (PDS) initiative was launched in 2014 to develop APIs that connect BRP’s systems to those of dealers over the Internet. The PDS APIs use the Standards for Technology in Automotive Retail (STAR) XML format. They are available only to dealers in Canada and the United States (often called “North American dealers”).
❗The PDS APIs are deprecated ❗
The Dealer Connect Program (DCP) was established in 2021 as the successor to the PDS initiative. The DCP APIs have transitioned from the STAR format to JSON for payload format. These DCP APIs are also available only to dealers in Canada and the United States.

This portal documents the new DCP APIs V3 and V4, which connect BRP dealers in all regions, not just Canada and the United States.
But why are there two different versions?
As of today (October 2025), the North American dealers and the other dealers have different back-end system versions, mainly in the SAP version (ECC vs. S4).
- DCP APIs V3 are for international dealers and support different languages and currencies.
- DCP APIs V4 are for North American dealers (Canada and the United States) and support only French, English, CAD, and USD.
When looking at API documentation on the portal, you will see if it applies to all versions or a specific version.
Dealer System Providers (DSP)
Throughout the portal, the term Dealer System Provider (DSP) names the entity (you) integrating an API.
The DCP APIs are targeted at two types of DSP:
- Dealer Management Systems (DMS)
- Customer Relationship Managers (CRM)
While both DMS and CRM could theoretically implement all DCP APIs, the functionality supported by a DCP API is targeted for a specific system, DMS or CRM.
The DCP APIs are documented in the API Catalog section. The documentation indicates whether the DCP API is targeted at DMSs or CRMs.
Why Develop APIs?
Why did BRP start developing APIs?
The short answer is to support BRP’s dealers' business operations and growth.
The main purpose of the DCP is to help dealers directly connect to BRP through their DMS and CRM to facilitate their operations and grow their business.
How exactly do the APIs help the dealer?
- Provide the dealer with accurate and real-time information on BRP products.
- Receive accurate and timely information from the dealer to help BRP build business programs that add value to the dealers.
- Provide a better client experience by using more efficient business processes.
- Facilitate employee onboarding for dealers since many, if not all, operations can be performed in one system.
- Improve the dealers' efficiency so they can spend more effort on growing their business.
API and Business Go Together

Since the DCP APIs' objective is to support BRPs and dealers' businesses, their integration in a DSP must also have the same objective.
That’s why, for many DCP APIs, the documentation includes DSP user and business requirements that will be validated during certification. DSP requirements are identified as “mandatory” or “optional,” with optional requirements providing added value to dealers.