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.
Provider:China MobileAsyncAPI: v3.0.0Spec: China Mobile OneNET event and callback surfaceOperations: 1Messages: 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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.