LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Mercedes Benz >> 2018 >> Sprinter 3500 Van Cargo Extended, 4WD >> Repair and Diagnosis >> TMC Recommended Practices >> Cost Control Methods >> RP 1612 - Service Event Data Transparency >> RP 1612 - Service Event Data Transparency >> Data Sharing Plan >> Service Provider: Repair Order/Case Detail
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Service Provider: Repair Order/Case Detail

This API should have ability to search all RO/Cases with data in a date range by customer. The API should have a viable and efficient way to have more than one RO/Case update (i.e., one incident vs. collection of incidents).

This GET web service endpoint fetches data for a single RO/Case based on the RO/Case's unique number. Provision for the following data elements or fields should be made accordingly:

NOTE: If a search request can return many RO/Cases (instead of just one as an embedded list vs. a secondary call), TMC recommends that the data be limited to no more than 300 ROs to ensure lean traffic and resource impact. The API should be versatile enough to get the detail by VIN, and then allow more data to be pulled, as needed. With restrictions, TMC recommends the API use virtual paging across the network. Error handling for dropped transactions should be built into the API to know if when unsuccessful events have occurred.