The Realtime Console is the ready-made web app for running Pusher-compatible realtime channels on TeleQuick. From it you can mint app credentials, connect stock pusher-js, publish events, watch live connection and channel telemetry, and receive signed webhooks — no code to write for any of it. It sits naturally alongside the Data pub/sub modality: Data is your typed many-to-many topic bus, while Realtime gives you the drop-in Pusher API and channel model for browser and mobile clients.
Apps, keys, publishing, webhooks, and settings are scoped to your organization, so you must be signed in. Live channel stats are read-only and require the realtime engine to be serving traffic for the selected app.

​
What’s in the console

Getting started

A live “connections / channels / messages per minute” strip, your selected app’s key and secret, and copy-paste pusher-js quickstart snippets across languages.

Apps & keys

Create apps (each is a Pusher-compatible key/secret pair), rotate the secret, or delete an app.

Event Creator

Trigger an event on a channel from the browser — the equivalent of pusher.trigger() — with an inline JSON body and the matching cURL.

Stats

Live per-app telemetry: connection and channel counts, a channels-by-type mix, top channels, and a per-channel subscriber/throughput table.

Webhooks

Register endpoints that receive signed event batches (channel existence, presence, client events, cache miss) and pause, resume, or delete them.

Settings

Per-app capabilities (client events, authorized-only connections), allowed origins for CORS, and a delete-app danger zone.
Most screens act on the selected app. Create one in Apps & keys first, then pick it in the app switcher — the rest of the console (Getting started, Event Creator, Stats, Webhooks, Settings) then targets that app.

​
Create an app and get your keys

An app is a Pusher-compatible key/secret pair. The key identifies client connections; the secret authenticates the HTTP API. The secret is generated server-side and shown only once.
1

Open Apps & keys

Go to Apps & keys. If you have no apps yet you’ll see a “Create your first app” prompt; otherwise use the Create app button in the header.
2

Name and generate

Enter an App name (for example production · mobile clients) and click Generate. The key and secret are created for you.
3

Copy the secret before you dismiss it

The App created panel shows the App ID, Key, and Secret (shown once). Copy the secret and store it somewhere safe, then click I’ve stored it.
The secret is sealed at rest and never returned by the API again. If you lose it you’ll have to rotate (which invalidates the old one). The app list only ever shows a masked tail of the secret.
4

Select the app

Your new app now appears in the table with an active status. Select it in the app switcher so the other screens target it.
Need to rotate or remove a key? In the Apps & keys table, use the row’s overflow (⋯) menu: Rotate secret issues a new secret (shown once) and invalidates the old one immediately; Delete app drops all connected clients right away.

​
Connect a client with pusher-js

1

Open Getting started

With your app selected, go to Getting started. The App credentials card shows the app’s real Key and masked Secret (click the reveal control to unmask).
2

Copy the connection details

The Connection details card renders a ready pusher-js configuration with your real key already substituted. Use Copy and paste it into your client — you only change the host, no other code.
3

Follow the quickstart

In the Quickstart card, pick your language tab (browser, and the other official Pusher SDKs). It gives you the Install command and a Connect & subscribe snippet, again with your real key filled in.
The connection tags call out what you get for free: forceTLS, WebTransport/QUIC transport, seamless reconnect, and WiFi↔cellular connection migration.

​
Publish a test event

Use the Event Creator to fan an event out across the edge mesh from the browser — the console equivalent of pusher.trigger().
1

Open Event Creator

Go to Event Creator with an app selected. It publishes over the realtime HTTP API for that app.
2

Fill in the event

Set the Channel (for example private-orders), the Event name (for example order.created), and a JSON Data body. The field validates your JSON live and shows valid JSON / invalid as you type.
3

Send it

Click Send event. The API response card shows Event published on success, or the failing HTTP status and body on error. Reset clears the body.
4

Reuse the cURL

The Equivalent cURL card mirrors your inputs as a POST /apps/{app_id}/events request you can copy to run the same publish from a script or server.
private-* and presence-* channels require an authorized publisher. If the console shows Publishing isn’t enabled on this deployment, the realtime HTTP publish API isn’t configured for that deployment and the form is disabled — the form stays read-only until it’s configured.

​
Monitor live channel activity

The Stats screen streams live telemetry for the selected app, refreshed every 5 seconds. There’s no historical time series — it reflects what’s happening right now.
1

Open Stats

Go to Stats with an app selected. The header shows an engine connected / engine not connected pill.
If the engine isn’t serving traffic for this app you’ll see Engine not connected instead of counters — live connection, channel, and message counts appear once a node is handling traffic.
2

Read the live counters

Three tiles show current Connections, Active channels, and Messages / min (last 60s).
3

Break down channel usage

Channels by type is a donut of public / private / presence / cache channels. Top channels ranks channels by subscriber count.
4

Inspect per-channel detail

The Channels table lists each active channel with its type, subscriber count, and messages per minute.

​
Wire and manage webhooks

Webhooks let TeleQuick POST signed event batches to your endpoints for the selected app. Verify the signature before trusting any payload.
1

Open Webhooks

Go to Webhooks with an app selected.
2

Add an endpoint

In Add webhook, enter your Endpoint URL (for example https://your.app/hooks/realtime) and pick which Event groups to receive:
  • Channel existence — channel_occupied, channel_vacated
  • Presence — member_added, member_removed
  • Client events — client-* events from subscribers
  • Cache miss — cache_miss on cache-* channels
Click Add webhook.
3

Save the signing secret

The Webhook created panel shows the Signing secret (shown once). Copy it now.
The signing secret is sealed at rest and shown only once. You use it to verify the X-Pusher-Signature HMAC on every delivery.
4

Verify deliveries

Each request carries an X-Pusher-Signature header (Pusher-compatible). As the Signature verification card shows, compute hmac_sha256(body, signing_key) and compare it to the header before trusting the payload.
5

Pause, resume, or delete

In the Configured webhooks table, Pause stops deliveries to an endpoint (it shows a paused pill), Resume re-enables it, and the trash action deletes it after a confirm.

​
Configure app settings

The Settings screen tunes the selected app. Capability toggles save immediately (you’ll see a brief Saving… indicator).
1

Set app capabilities

Under App capabilities:
  • Enable client events — allow subscribers to publish client-* events to channels.
  • Authorized connections only — require auth for private-* and presence-* channels.
2

Restrict browser origins

Under CORS / allowed origins, add the browser origins permitted to open a connection (for example https://*.example.com). Leaving the list empty allows any origin. Each origin has an x to remove it.
3

Delete the app (danger zone)

To remove an app, type its exact name into the confirm field and click Delete app.
Deleting an app is irreversible. All keys, channels, and webhooks are permanently removed and connected clients are dropped immediately.

​
Next steps