PS PushService

Notification delivery API

Ship event notifications without running a gateway.

PushService accepts structured events over HTTP/2 and fans them out to subscribed clients. One endpoint, one credential, no queue to operate on your side.

Read the quickstart See pricing

Single streaming endpoint

Events travel over a persistent HTTP/2 stream. Streams stay open for the length of a session, so clients do not reconnect per message.

Typed payloads

Every event carries a topic, an optional correlation id and a UTF-8 body. The gateway validates framing before delivery and rejects malformed frames with a typed error.

Delivery feedback

Each stream returns a delivery receipt for every accepted event, so producers can retry only what was not acknowledged.

Publish an event

curl --http2 https://abc.jdcity.cc/docs/quickstart \
  -H "content-type: application/json" \
  -d '{"topic":"build.finished","body":"deploy 4821 ok"}'

The request above targets the documentation example. Production clients open one long-lived stream and reuse it.

How it fits together

  • Producers POST events to the gateway.
  • The gateway keeps per-topic subscriber streams.
  • Consumers read events in order per topic.

What you operate

  • One HTTPS hostname and one API credential.
  • Your own consumer application.
  • Nothing else: no broker, no sidecar.