How a Modern Open Platform Bridges Enterprises Like a Wormhole

“Wormhole” – in physics, a tunnel connecting two different space‑times, analogous to the channel we are building to connect large enterprise customers to our open platform.

Why an Open Platform Is Needed

What Is an Open Platform?

An open platform is a company’s external window that exposes internal standards, data, and services as APIs for third‑party developers, essentially a business‑core platform opened to the public for collaborative integration.

The enterprise open platform, built on freight‑business capabilities, offers external partners access to core business APIs, account management, data subscription, and more.

Its mission is to deliver pricing, transaction, logistics, and other foundational services to merchants, third‑party developers, and service‑provider platforms.

The Value of an Open Platform

The core value lies in mutual benefit between our services and third‑party applications, enhancing overall user experience and platform stickiness.

Expose core product services to third‑party developers, creating a complete product ecosystem through cross‑industry capability sharing.

Generate revenue for third‑party platforms, independent developers, and partner customers via data exchange and collaborative wins.

What Kind of Open Platform Is Required

Current State of HuoLala

After extensive business refinement and technical upgrades, we have built an industry‑leading standard‑process open platform covering direct‑customer freight scenarios.

Platform Architecture

Access Process

Customer Characteristics

Standard process serves 80% of standard customers; standard + custom serves 15% of custom customers; platform integration serves 5% of large platform customers.

Standard Customers

Features: Standard process integration, almost no customization, meets all needs.

Advantages: Low maintenance cost, stable GTV revenue.

Drawbacks: Limited revenue per customer.

Custom Customers

Features: Mostly standard process but with customization requirements.

Advantages: Higher GTV revenue.

Drawbacks: Higher maintenance cost, continuous new custom demands.

Platform Customers

Features: Bypass standard process, provide their own platform with minimal changes.

Advantages: Large GTV potential, high traffic, rapid enterprise growth.

Drawbacks: High integration, joint debugging, testing, and acceptance costs.

Challenges Faced

How to handle platform customers?

Problem Analysis

Insufficient Support: Standard process is weak in this scenario.

Role Reversal: The integrator becomes the platform, and the platform becomes the integrator.

Reverse Integration: We integrate external platforms instead of them integrating us.

Dealing with Conflict

Retreat/Avoidance: Put aside current or potential conflicts.

Force: Impose a solution at the expense of others, suitable for zero‑sum games.

Resolution: Define, collect, and solve problems to achieve win‑win or multi‑win outcomes.

Exploration Directions

Platform Research

Comparative analysis shows most platforms share similar onboarding processes, request/response formats, protocols, and authentication, with minor differences in parameters.

System Planning

Background

Insufficient Reusability: Each integration starts from scratch.

Lack of Flexibility: Growing platform variety leads to large parameter differences.

Weak Governance: Inadequate client management, permission control, traffic monitoring, and alerting.

Poor Joint‑Debug Environment: Misaligned bilateral debugging slows progress and limits subscription message completeness.

Goals

Lightweight Onboarding: Identify business, apply policy authentication, adapt parameters, orchestrate capabilities, and build reusable assets to continuously lower integration cost.

Capability Orchestration: Combine pricing, marketing, order, payment, etc., to support differentiated processes for large customers.

Governance Construction: Implement client and API permissions, monitoring, alerts, and data statistics to reduce system risk.

Self‑Service Troubleshooting: Provide API debugging, signature generation, and SDK auto‑generation tools to cut communication and resource investigation costs.

Core Construction

Customer Management

Platform Management

Audit mechanism: Only approved external platforms can call core services, ensuring security.

General configuration: Visual management of keys, payment methods, callback URLs, guidance info, status mapping, etc.

Platform Authorization

Customer authorization via unified H5 page, adaptable for embedding in external apps (Feishu, DingTalk, etc.).

Authorization callback pushes binding results to partner platforms; active query allows partners to verify and compensate.

Business Adaptation

Model Adaptation Long order flow involves address parsing, vehicle conversion, payment methods, broadcast duration, driver guidance, order remarks, pricing transfer, etc. Service‑provider platform parameters are normalized into a standard model for reuse.

Capability Orchestration Atomic capabilities (address, pricing, verification, coupon, order, payment) combine into platform capabilities, which can be further extended to meet diverse demands.

Efficiency Tools

Reference industry‑leading solutions to build auxiliary tools that accelerate large‑customer onboarding and reduce cost.

Gateway Configuration

Unified interface and maintenance: Consolidate M platforms × N interfaces into a single set.

Identify identity, unify monitoring, lower maintenance cost.

Sentinel Integration

Traffic control:

Customer‑level rate limiting (overall control).

Interface‑level rate limiting (per‑API control).

Resource quota limiting (per‑API resource control).

API Debug Console

One‑click debugging of call chains. Generate context‑linked parameters, send requests, receive platform responses. Auto‑generate signature parameters for encrypted communication, improving joint debugging efficiency.

Self‑Service Troubleshooting

Real‑time query of detailed error codes reduces latency of manual updates.

Accurate problem location lowers coordination cost between parties.

SDK Generation

Basic SDK modules include:

Communication protocol encapsulation.

API contract encapsulation (parameters, timestamps, signatures, codes).

Request‑parameter model encapsulation.

Response‑parameter model encapsulation.

Automatic code generation based on API metadata and DSL templates, supporting multiple programming languages.

CI/CD pipelines automate SDK build, test, and release, providing versioned SDKs for developers.

Monitoring of API metadata changes triggers automated regeneration and deployment.

Message Push

Broadcast Push : Basic subscription capability; service providers push messages to configured endpoints.

Targeted Push : Preserve original messages, ensure complete push chain, and offer multiple strategies for development, issue detection, and compensation.

Summary & Outlook

Abstract platform integration reusable capability for low‑cost onboarding of more service providers.

Flexible model adaptation and capability orchestration for efficient handling of differentiated workflows.

Establish basic governance to mitigate over‑privilege risks.

Support visual self‑service troubleshooting to reduce development, debugging, testing, and acceptance costs.

Enhance interface security and reliability through permission control and idempotent requests.

Build a rich monitoring system to assist rapid issue investigation and real‑time status awareness.

Like a “wormhole,” as these capabilities mature we gradually open channels to large‑customer platforms, achieving efficient inter‑platform connectivity.