Subscribing & the app
Receiving is accountless. A topic’s subscription link is the only credential:
https://app.pinglet.co.uk/<namespace>/<name>/<key>
Anyone holding the link can subscribe; nobody can guess it. Every topic key is minted with a cryptographically random suffix, and there is no way to bring a chosen key into existence.
Subscribe in the app
Install Pinglet for iOS or Android, then any of:
- Open the link on your phone — it deep-links straight into the app (iOS Universal Links / Android App Links).
- Paste the link into Add a subscription.
- Scan the QR code — every topic’s dashboard page shows one, and any subscriber can display a QR for a topic they hold.
From then on, every message published to that topic arrives as a native push. The app shows per-topic history and lets you unsubscribe at any time.
Share a subscription
The url in every publish response is the share link. In the app, any subscription you hold can be shared onward — copy its link or show its QR. The link is the capability; treat it accordingly (share it in private channels, not public pages).
Read history over HTTP
Anyone with a topic’s key can read its recent history — useful for scripts and dashboards:
curl "https://app.pinglet.co.uk/v1/acme/<topic-key>/messages?limit=50"
limit— page size, default 50, max 200.since=<message id>— sync cursor: returns messages with an id greater thansince, oldest-first, so a client can page forward without gaps. Withoutsinceyou get the latest messages, newest-first.
History depth follows the publisher’s plan: 24 hours on Solo, 30 days on Pro. Pinglet is a relay, not an archive — expired messages are deleted.
Watch live in a browser
A topic’s public feed is browsable at its subscription URL, and updates live over server-sent events:
GET https://app.pinglet.co.uk/<namespace>/<topic-key> # feed page
GET https://app.pinglet.co.uk/<namespace>/<topic-key>/events # SSE stream
Good to know
- Subscribing requires the topic to already exist; only key-holders can create topics.