- Home
- Docs
Pong Chat developer docs
Everything you need to put Pong Chat on a site and connect it to your own systems.
Pong Chat has two halves you can program against:
- In the browser —
pong.js, a small loader that adds the chat to your page. You talk to it through one function,Pong(...): open or hide the chat, pass user data, listen to events. - On your server — a REST API to read clients and their messages and to send messages as an agent, and webhooks that post every new message to your endpoint, signed with HMAC-SHA256. Both are part of the Premium plan.
Keys
All keys are in the desk under Settings → API keys (admins only).
| Key | Where it goes | Secret? |
|---|---|---|
| Public key | In the widget’s script address, js.pong.ee/<key>; the user part of REST auth | No — it is in your page source |
| REST secret | The password part of REST auth | Yes — server only |
| Identity secret | Signs verified user identity | Yes — server only |
| Webhook secret | Verifies the X-Pong-Signature header | Yes — server only |
Secrets are shown once when you generate them. Regenerating one invalidates the old value immediately.
Hosts
| Host | What |
|---|---|
js.pong.ee | The loader, at js.pong.ee/<your key> (older snippets: call.pong.ee/pong.js) |
chat.pong.ee | The widget iframe and its WebSocket |
app.pong.ee | The agent desk and the REST API (/api/…) |
files.pong.ee | Uploaded files and images (unguessable URLs) |
Where to go next
- Install the widget — the snippet and platform notes.
- JavaScript API — every
Pong(...)method. - Events — react to messages, unread counts and open/close.
- PongSetup options — look, placement and loading.
- Verified identity — the same history on every device.
- REST API and webhooks.