Skip to main content

Customer Detail Push Service API (LDEx) – Overview

1. Purpose​

This service enables authorized partners to receive customer-level information directly from UnitedHealthcare’s Small Business Administration systems. Instead of manually collecting data from multiple sources, partners receive a bundled summary of key customer details—such as demographics, coverage types, and plan information—delivered automatically and securely.

2. Who Can Use This Service​

This service is useful for:

  • Brokers, agents, and third-party partners managing small-business client data
  • Partner onboarding teams creating training materials and process guides
  • Product managers and strategists analyzing customer data flows and coverage trends
  • Sales, marketing, and compliance teams referencing customer data workflows in non-technical contexts

It supports both technical and non-technical roles involved in managing customer relationships and coverage setup.

3. What Information is Available​

The service provides broad, easy-to-understand categories:

  • Customer demographics: Basic identifiers such as name, address, and group details
  • Policy and contract information: Summary of coverage status and product line
  • Coverage categories: Benefit types such as medical, dental, vision, basic life, and AD&D
  • Plan information: High-level indicators of selected plan offerings
  • Rates information: General premium or cost cues (not detailed rate tables)
  • Transmission summary: Reference identifiers and status messages for tracking

No technical formats, authentication steps, or error codes are exposed in this version.

4. Benefits of This Service​

  • Centralized access: Receive all relevant customer details in one package
  • Consistent terminology: Everyone uses the same categories across channels
  • Timely updates: Data reflects the latest customer status and coverage changes
  • Streamlined workflows: Automatically receive data without manual lookups
  • Flexible applications: Useful for quoting, onboarding, planning, and training

5. Example Uses​

  • A broker receives customer demographics and coverage details before a client meeting, enabling informed discussions.
  • A partner team creates a reference guide outlining what data is received during onboarding.
  • A strategist monitors coverage trends across regions using summary data from multiple customer packages.
  • A training document explains how customer data is delivered in one step, simplifying onboarding and quoting.

6. Important Notes​

  • This overview omits technical details such as authentication, data formats, and error codes.
  • Access to the service requires a formal partnership and onboarding process.
  • Data categories and formats may evolve over time; treat summaries as current snapshots.
  • The data structure and identifiers are proprietary and confidential.
  • If a data push cannot be completed (e.g., missing context or unrecognized partner), the system provides clear, human-readable feedback.