Quickstart: your first notification or verified answer

For a notification, start with the route that fits your sender. Complete one message receipt on your own phone; use a protected Topic when an Agent needs your answer. The connection animation illustrates protected Topic pairing.

• Public Topic: first message
• HTTPS push tutorial

With an existing public Topic, follow the public guide to check its name, send a non-sensitive message and confirm phone receipt. The phone must own or have confirmed following the Topic; visiting its webpage is not a subscription. For a non-public notification, use the complete private link from phone HTTPS Push and follow its hello walkthrough.

The service can read HTTPS input; use the protected CLI route below when content must be encrypted at the sender.

• Check public downloads
• Phone hello walkthrough

Install Ntfyx on iPhone or Android and the CLI on Windows, macOS or Linux. Android background push requires Google Play services. Follow the installer for your OS, then check ntfyx version. The commands below work once the CLI is installed on any of these desktop platforms; use the PowerShell installation instructions on Windows.

No Ntfyx account is required, but your phone must authorize this sender.

ntfyx version --json
ntfyx connect

• Install for your OS
• Phone apps and version requirements

Keep ntfyx connect running, choose the private Topic connection option on the phone and scan the fresh QR on your trusted computer. Confirm the Source and choose a protected Topic; when creating through pairing, follow the connection flow offered by your installed version. A public link is not a pairing code.

Once connected, run topics and note the local CLI alias. Replace Work below if your listed alias differs.

ntfyx topics

• Creation and pairing troubleshooting

Send this non-sensitive test and open its Topic in the phone Inbox. Confirm that Build 42 passed appears. CLI success means acceptance by the service; phone foreground synchronization, background push and a system banner are separate observations. Foreground Inbox synchronization can work even when system notification permission is declined.

ntfyx send "Build 42 passed" --topic Work --json

• Message received without an alert

Keep the terminal waiting, open the original question on the phone and choose Allow or Deny. This command demonstrates a question; it is not connected to a deployment, payment or external action. Synchronous ask verifies the answer at the original Source and acquires its one-time claim before returning an allowed result.

Deny is a complete answer; a timeout is not consent and a late answer cannot restart an ended job.

ntfyx ask "Continue this harmless demo?" --topic Work --allow-deny --wait 60s --expires 90s --json

• Connect your Agent
• Signed answers and execution boundaries

Open the Web Inbox and authorize its fresh QR with the primary phone. The browser receives independent receiver keys and reads new messages addressed to it after authorization; it does not inherit old phone history. Keep the page open for updates. A public Topic webpage does not need this pairing step, and its content is public.

• Open Web Inbox
• Follow the troubleshooting checks