Dealer and OEM support STAR API

  • Release version: Australia
  • Updated July 14, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Dealer and OEM support STAR API

    The STAR API enables automotive OEMs and their dealer networks to streamline warranty claim processing by automating the retrieval and submission of repair order data from diverse dealer management systems (DMS). This integration addresses the challenges of manual data submission, inconsistent data formats, and the need for multiple custom integrations across dealers.

    Show full answer Show less

    Key Features

    • Standardized Data Retrieval: The STAR API, configured within the Dealer Integration Framework, pulls repair order details—such as repairs performed, parts and labor codes, and external services—directly from each dealer’s DMS using a STAR-compliant SOAP endpoint.
    • Automated Claim Creation: The retrieved repair data is used by the MCO (Manufacturing Claims Operations) system to automatically generate warranty claims, eliminating manual claim entry by the OEM.
    • Real-time Monitoring: The integration tracks claim creation status as repair order data is received, providing visibility into the claims process.
    • Standardized Integration Across Dealer Network: By leveraging the STAR API standard, the OEM avoids building and maintaining separate custom integrations for each dealer’s DMS platform.

    Benefits

    • Increased Efficiency: Automates warranty claim creation, reducing manual workload for both dealers and OEM staff.
    • Consistency and Accuracy: Standardized data formats from STAR API reduce errors and inconsistencies caused by different DMS platforms.
    • Scalability: Supports a fragmented dealer network with various DMS platforms without requiring individual custom integrations.
    • Improved Visibility: Enables real-time tracking of claims, facilitating better management and faster resolution.

    Practical Application for ServiceNow Customers

    ServiceNow customers working with automotive OEMs and dealers can leverage this STAR API integration approach to automate warranty claims processing. By incorporating STAR API configurations within their dealer integration frameworks, they can streamline claim workflows, reduce manual data handling, and improve data accuracy across disparate DMS systems. This results in faster claim turnaround and reduced operational overhead.

    Use case scenario demonstrating dealer and OEM support for warranty claims using the STAR API.

    Scenario

    Alectri, an automotive OEM, relies on its dealer network to submit repair order details for warranty claims. A customer brings a vehicle to a dealership for a covered repair. The service advisor then creates a repair order in the dealer management system (DMS) for a technician to investigate. The technician identifies the parts and labor required, fixes the vehicle, and updates the repair order in the DMS with the labor and parts used.

    Turning that repair order data into a claim, across a dealer network where each dealer's DMS captures the data differently, creates several challenges:

    • Manual data submission: Dealers manually submit repair order details to the OEM to create each claim.
    • Manual claim creation: The OEM manually creates the claim from the submitted repair order details.
    • Fragmented dealer network: Dealers on different DMS platforms submit repair order data in inconsistent formats.

    Solution

    Alectri configures the STAR API in the Dealer Integration Framework to retrieve repair order details directly from each dealer's DMS. MCO for Warranty Claims uses this data to automatically create the resulting claims. The integration follows four phases:

    1. Configure: Set up the STAR API configuration in the Dealer Integration Framework using the STAR-compliant SOAP endpoint.
    2. Retrieve: Pull repair order details from the DMS, including repair performed, part codes used, labor codes used, and external services used.
    3. Create: Automatically create a claim in MCO using the retrieved repair order details.
    4. Monitor: Track claim creation and status in real time as repair order data arrives from each dealer.

    The Set up inbound DMS integration describes how to set up the STAR API configuration and map STAR XML payloads to MCO records.

    Benefits

    Compare the impact of using MCO DMS integration.
    Table 1. DMS integration benefits
    Without MCO With MCO DMS integration
    Dealer submits repair order details to the OEM to create a claim. The STAR API configuration built in the Dealer Integration Framework retrieves the repair order details.
    OEM creates the claim from the submitted repair order details. MCO automatically creates the claim using the retrieved repair order details.
    OEM builds and maintains a separate custom integration for each dealer's DMS. OEM uses the STAR API, a standard supported across the dealer network.

    Outcome

    After the technician updates the repair order in the DMS, Alectri's STAR API configuration in the Dealer Integration Framework retrieves the repair order details. MCO then automatically creates the claim using the retrieved details, without manual submission or a separate custom integration for each dealer.