AsyncAPI channel · China Mobile · China Mobile OneNET event and callback surface

/

Before a push instance goes live, OneNET issues an HTTP GET to the registered address as ?msg=xxx&nonce=xxx&signature=xxx. The receiver verifies signature and must echo msg back verbatim, otherwise the instance stays in 验证失败 (validation failed) and no messages are delivered.

Open source AsyncAPI → All China Mobile channels China Mobile provider profile
Provider: China Mobile AsyncAPI: v3.0.0 Spec: China Mobile OneNET event and callback surface Operations: 1 Messages: 1

Channel address

/

Operations

receive
receivePushInstanceValidation
Answer the OneNET push-instance address validation challenge.

Messages

ValidationChallenge
Push instance validation challenge
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.