ntfy is push notifications reduced to their essence: a topic URL you can publish to with curl and subscribe to from any device. xengo publishes to it the same way — each click and QR scan arrives as a message on your topic within seconds, whether that topic lives on ntfy.sh or on a server you run. No account on their side, one pasted URL on ours.
There's no token exchange and no app registration because ntfy doesn't want one — a topic URL is simultaneously the address and the credential. xengo posts your scan messages to it; anything subscribed to the topic gets them.
In the ntfy app (or web app): Subscribe to topic, and invent a name nobody would guess — scans-x7k2m9 beats scans. Your topic URL is https://ntfy.sh/<topic>, or the same path on your own server.
Console → Notifications → Add channel → ntfy. Paste the full address into the Topic URL field, save — then hit Send test and watch the message pop on every subscribed device.
One topic for the whole account, or one per concern — attach channels per link and QR code, so the conference-badge codes publish to one topic and the packaging codes to another.
QR codes go where servers can't watch — posters, packaging, badges. Publish their scans to an ntfy topic and the physical world reports in: style the code in the console, print it once, subscribe from anywhere.
Notifications attach per link as well as account-wide. Open any link, tick the ntfy channels that should hear about it, and the next scan publishes there — one topic per project stays perfectly quiet about everything else.
xengo POSTs the message as plain text with a Title header — exactly the publish call ntfy documents for curl — so it works with ntfy.sh and any self-hosted instance alike.
The channel needs nothing but a topic URL. Move the topic to your own ntfy server later and only the pasted URL changes.
Title names the short link; the body carries the link title, source (click vs QR scan), destination, UTC time, device and your tags.
Redirect plane, event processing, publish — the message typically reaches subscribers within a couple of seconds of the scan.
If the publish fails, xengo retries on a backoff ladder for up to six attempts, with every attempt recorded in the delivery log.
The topic URL is validated as http(s) when you save the channel, so a mangled paste fails at set-up instead of failing silently later.
Really. On ntfy.sh, topics exist the moment someone publishes or subscribes to them — no sign-up on either side. You paste the topic URL into xengo, subscribe in the ntfy app, and that's the entire integration.
Yes — the Topic URL field accepts any http(s) address, so https://ntfy.example.com/scans works exactly like ntfy.sh. Your server does need to be reachable from the internet, since xengo publishes from the cloud.
On ntfy.sh, anyone who knows the topic name — the name is the credential, so make it unguessable. Note that xengo publishes without auth headers, so the topic must accept anonymous publishes; on a self-hosted server you can grant anonymous write to just that topic and lock down the rest.
A title of 'xengo: <short-link> clicked' and a plain-text body with the link's title, the short URL, whether it was a direct click or a QR scan, the destination, the UTC time and — where available — device, referrer, IP and your custom tags.
Failed publishes retry on a backoff ladder — up to six attempts over roughly 43 minutes — with each attempt visible in the delivery log. And ntfy gets the readable text by design; for the full structured event with signature headers, run the generic webhook channel alongside it.
Smart URLs, dynamic QR codes and a full API — branded on your own domain, safety-screened, and tracked. Build, re-point and measure it all in one place.
Start free trialBranded short links on a domain you control — editable, screened, and tracked.
Branded QR codes you can re-point any time — never reprint the poster again.
$ curl -X POST api.xengo.io/v1/links { "domain": "go.acme.com", "url": "https://acme.com/…" } → 201 go.acme.com/aB3xK▋
Create and manage links + QR at scale, straight from your own tools.
14-day free trial, card required, cancel anytime. Invent a topic name, paste the URL, and the first message is seconds behind.
