¿Qué hay de nuevo?

In the Dealer Authentication API, added a simulation mode available in the QA environments. Updated step 1 to use an API call instead of manually creating the URL to open the BOSSWeb login page.

In the CRM Activity Log, clarified the sales opportunity status mapping to the internal CRM status.

The CRM Activity Log API documentation was created and removed from the DSP Information API documentation. Have the CRM Activity Log function in the DSP Information API documentation was confusing.

Updated the What's Coming? section to remove the Sales Opportunity API and add the Dealer Units Inventory API.

In the API Catalog section, added the list of APIs usable by a CRM.

In the DSP Information API, finalized the CRM Activity Log payload.

In the Sales Opportunity API, finalized the payload and the certification tests.

In the Dealers API, removed the S0 Standard Ground shipping method.

In the Parts Order API, removed the S0 Standard Ground shipping method.

In the DSP Information API, added the CRM Activity Log service.

In the Parts API, updated the part numbers to be used for some tests.

Completed the documentation for the new Sales Opportunity API.

In the Parts API, added more information on the kit and sales BOM parts. Also improved the supersession documentation and the usage of the valid_from date.

In the Parts Inventory API, add a description of the availability status codes.

In the Retail Transactions API, added the list and description of the test cases performed during the Test and Dealer Pilot phases.

In the Units API, the trailer object for the Switch products was added to the response. The trailer object includes the trailer's description and prices. The trailer prices are added to the Switch prices.

In the Invoices API, added the delivery_nos query parameter to retrieve invoices using one or many delivery numbers. Also fixed the supercharge_value field, which sometimes included the handling_fee_value field.

In the Parts Order API, added that a parts order can not be modified once it's created.

In the Retail Transactions API, added more information on how to handle warranty jobs. Also, added information on the transaction numbers.

In the Trail Balance API, the end points for the authentication and to send data have changed. The provider, Jackson Dawson, has changed "BRP RISE" to "TrueTrack".

In the Units API, corrected the description of the U8 and UI sales status code. Also corrected the problem that made some data missing.

In the Units API, added the package_label and model_description fields.

In the Dealer Parts Inventory API, added a limitation to indicate that a part number with a '-' can't be used to call the Find Part (Part Locator) service.

In the Dealer Authentication API, fixed the response payloads.

In the Invoices API, remove the cost_value property since the value is never good.

In the Parts API, added the is_bom property to indicate if a part number is a kit (BOM).

In the Parts Order API, the dealer PO number property now accept only letters, numbers, and spaces. Special characters are not allowed.

In the Parts Order API, added the backorder endpoint to retrieve the orders with backorder parts.

In the Units API, added the brand in the payload and in the query parameters.

In the Dealer Authentication API, add information on the "state" query parameter that can be used to send information to the callback.

In the Parts API, added the product type 80 for the manuals. Clarified that the "last change date" query parameter must be at least one day before the current date.

In the Parts Order response, remove the trackings object since it's always empty.

In the Retail Transactions API, the usage of the additional_costs field was clarified. Clarified that the optional properties in the payload must be sent if they are available in your DMS. The transaction must include additional costs if the total customer price differs from the MSRP. Corrected the labor rate calculation with a fixed cost example. Clarified the tax calculation when only the total invoice value is known.

The Units API that returns the unit catalogue with description, characteristics, prices, and links to images and technical documents.

The Units Order API that returns the list of unit orders for a dealer.

In the section Order, Invoice, and Delivery, corrected the example for "Multiple Deliveries From Multiple Orders". Modified the examples for the new Parts Order API without the tracking object. Updated the "Tracking the Shipping" section to use the delivery information from the Deliveries API.

In the Dealers API, added the Electric Vehicle (EV) qualification level, the business and service hours, and sales zone information. Also update the requirements to indicate that the Dealers API can be called when needed to retrieve the dealer's information, for example when entering the Parts Order screen.

In the Dealer Parts Inventory, clarified the Function Requirement ID 1 to indicate that the dealer's parts inventory must be automatically sent without a dealer manual action. Added Functional Requirement ID 8 to indicate that the API must be called with a full dealer's parts inventory and not one part at a time.

In the Deliveries API, removed the time from the last_change_date_from and last_change_date_to parameters. Indicate that the Deliveries API CAN NOT be used to retrieve unit deliveries. Added information on what to do when the order quantity and delivery quantity are zero.

In the DSP Information API, added documentation on the status 404 Not Found.

In the Invoices API, the maximum value for the limit parameter is 200. Add the invoice_type and invoice_types parameters to the Get Invoices endpoint. Removed the time from the invoice_date_from and invoice_date_to parameters.

In the Parts API, changed the examples to use the V4 version. As requested by many dealers, added the units_of_measure object that contains all the part's measures, like weight and length. IMPORTANT: Only available in the V4 version. Added in the functional requirement ID 1 that no manual action from the dealer is required to update the parts catalogue. Added mandatory functional requirement 7 to display the part's measures to the dealer. Added a recommendation to call the Parts API monthly to get the changes from the last 30 days to avoid missing updates. Added explanation on the difference between the last update date and the valid from date.

In the Parts Order API, added the 'expedited' order type. Added the 'summary' parameter to the Get Orders end-point to retrieve a summary of the parts order. Added the Get Order end-point to retrieve a parts order based on the sales order number. Added explanation and examples of retrieving parts order using the 'summary' parameter to avoid timeouts. Corrected the type for the quantity fields in the query and response payloads: the quantity is an integer and not a number. Added functional requirement 18 (optional): The dealer should be able to retrieve a single parts order using the sales order number. Added functional requirement 19 (optional): The dealer should be able to retrieve parts order summaries.

In the Promotions API, added the section "Understanding Promotions" to provide more examples on the stackable bulletins and more BOSSWeb screen examples.

In the Retail Transactions API, clarified the requirement for the data transmission: no manual dealer action must be required. Added more information on taxes for the parts transactions and how to handle trade-ins in a unit sale. Modified the "rate" field in the additional cost to allow for a negative number.

In the section Order, Invoice, and Delivery: The Complete Story, added an example of parts receiving using the invoice as the entry point.

In the Parts Order API, added the section Order Status to explain the global order status vs the item status. Also clarified DSP Requirements 10 and 11.

In the "Authentication and Credentials" and "Application Authentication API", added that if you worked on the DMS Information or Sales Opportunity V2 APIs, you already have your Application Authentication credentials.

The section Start Here With Mandatory Reading! that provides important information on DCP and the BRP dealers.

Add the section Important: BRP Dealer Operation Standards and Certification that you have to read!

In the Certification Process and Getting Support sections, added information on making sure to use the DCP Certification and Support portal.

In the Parts Order API, added the status on_hold in the header_statuses field of the response. Simplified the delay between calls to the Check service. Added information on the dealer authentication token that must match the dealer number. Also added information and requirements (requirement 17) on displaying the shipping_lines field instead of the ordered_lines field.

In the Retail Transactions API pages, removed mention of V5, the API is V3/V4. Clarified that additional costs that are not included in the total customer price must bot be included in the payload.

In the Warranty Claim API, added missing description for the work_order field.

At the start of each API Catalog section, add the section "Where to Start? Read Me First!" to list the general sections that must be read before started developmen tof an API.

In the Certification Process section, added that the Jira certification ticket must be created only when you start work on an API. Do not use the DCP Jira as a backlog of the work to be done.

In the Trial Balance API, change the field format for the amounts to ±99999999.99 (one less number) since the maximum amounts supported is +/- 99,999,999.99$. Also added that the account nume rand description can't be empty.

In the Technical Information page, in the Error Handling Overview, added information for the status 400 handling: do not send back the payload until the error is corrected.

In the Parts API, clarified the requirements to indicate that the complete parts catalogue must be loaded in the DMS and made available to the dealer.

In the Retail Transactions API, indicates that the total customer cost includes all the additional costs. Also, must use a new UUID if the payload is resent after an error and added information on some error 400. Add information on how the payload exceptions will be managed if a DMS can't send all the requested information.

The Trial Balance API documentation.

In the Unit Warranty Coverage, remove the coverage_status field since the value is always "active".

In the Certification Process, added a warning to not disable the email notification in your Jira account! Added information on how to change a certification ticket state.

In the Deliveries API, the customer_po_no property has been renamed to dealer_po_no to be aligned with the other APIs. Also returns a status 400 if the dealer number is invalid. Added an optional requirement to get the list of deliveries daily.

In the Parts Order API, added information that the sales_order_no property is empty in the Validate response and the Check response for a Validate request. The response returned by the Check service doesn't contain the list of partners. Added information that a timeout can occur with less than 25 items.

In the Parts Order API, added a requirement on the BRP-specific information to be displayed.

The Invoices API now returns a status 400 if the dealer number is invalid.

In the Retail Transactions API, added tests in the DSP Requirements section to send production data to the test environment. To help the transition between the V2 and V4 backend processing, added the requirement to keep the V2 API alive until asked by BRP to shut it down. Add tests to compare invoices in the DMS versus the received data.

In the Retail Transactions API, the transactions.jobs.time_cards.labour_rate property is now optional. Added information on add to handle fix price jobs. The property transactions.units.additional_costs is now mandatory.

In the Parts Inventory API, updated the examples and the parts used for the tests.

The Promotions API used to retrieve unit promotions.

The Unit Warranty Coverage API allows the dealer to retrieve a unit warranty coverage status.

In the Welcome section, removed the notion of V5 APIs. V3 APIs are for International and V4 APIs are for North America.

In the Technical Information section, updated the string information in the Response Payload Format section: if the information is not available for a string, an empty string is returned ("") and NOT as "NA".

In the Certification Process section, the description of the DCP JIRA used to request certification activities was added.

In the Getting Support section, the description of the DCP JIRA used to request support and ask questions was added.

In the Certification Process, added precisions on the quality assurance and dealer pilot phases: automation must be active and production level code must be used.

In the API Catalogue, aligned all the error message payloads to the standard described in the Technical Information section.

In the Campaigns API, added a requirement that a message must be shown to the user when the unit has no active campaign.

In the Dealer Parts Inventory API, section Dealer Parts Inventory Payload Size, information on the 30,000 items payload limit and the related requirements and tests. Also clarified when to send the dealer's parts inventory data updates every day, even if the dealer is closed.

The Delivery API is now available to retrieve unit and PA&A delivery documents for a dealer.

In the DSP Information API, added requirement for dealer management.

The Invoices API is now available to retrieve unit and PA&A invoices for a dealer.

In the Parts API, added information on when to call to update the catalogue. Clarified the requirement that the daily update must be automated. Added information on the "in package" quantity. Added information on prices when a part is obsolete. Added requirement to find a parts order using a delivery number or an invoice numner.

In the Parts Inventory API, corrected the JSON example to have the prices as number and not string.

In the Parts Order API, add the missing language table. Add the Dealer-Number header parameter for the Check Order call. Add information on the Check service that can be used after a Validate and that the validation must be done for all orders, even those with more than 30 items. Also added requirements to retrieve the parts orders using Get to have all of them in the DMS database.

In the Retail Transactions API, added missing job codes definition.

In the Unit Specifications API, added that the last_status_date property may be null if the date when the status was last changed is not available. Added that a dealer can ask for information on any VIN, even if they don't have it in their inventory.

new fields in the Unit Specifications API response.

the Parts Order API documentation is finished.

the Dealer Authentication information and API to add information on the redirect URL.

information on the paging mechanism used by some APIs.

the Warranty API documentation.

the Parts Inventory API documentation is finished.

the Retail Transactions API document is finished.

the Dealer Parts Inventory API requirements.

the list of international shipping methods.

the name mapping between the DCP APIs V2 and V3/V4/V5 on the API Catalogue page.

section "What Changed From V2" for all APIs that are changed from the DCP APIs V2.

section "What's Coming?" on the Welcome page to list the upcoming DCP APIs.

in the section Data Sharing a precision on the data sharing consent.

in many API sections that all the number fields with decimals use the dot(.) as the decimal separator. The coma (,) is NOT supported as a decimal separator.

in the Parts API documentation: . A part may be in more than one supersession chain. . Added the sales organization and currencies for V4. . Added validation tests for an invalid part number, a part with missing prices, a vintage part, and an obsolete part.

Section "Navigate the Site"

DSP Information API: added clarification to send only PowerSports dealers. Updated the requirements and validation tests.

Campaigns API documentation.

Articles API documentation.

Retail Transactions API documentation not finished.

Parts Order API documentation not finished.

Sales Opportunity, Automatic Purchase Order, and Warranty Claim APIs are not documented yet.

First release of the DCP portal.