Pharos / Docs / v0.5.10

Signal notifications through your own bridge

Updated 2026-09-08 · Pharos 0.5.10

Requirements

A separately operated signal-cli-rest-api bridge, a registered sender account and a test recipient. Pharos does not register or host a Signal account. Hosting and securing the bridge are separate from installing Pharos.

1. Expose the bridge through HTTPS at /v2/send. Configure the reverse proxy to validate a bearer token before forwarding requests. Do not expose an unauthenticated send endpoint.
2. In Admin → Integrations, add an endpoint and choose Signal (own bridge).
3. Enter the bridge URL, sender number in international format, recipient number or group ID, and the bridge bearer token.
4. Save and use the endpoint test action. Verify receipt on the intended device.
5. Create and resolve a public test incident. Verify delivery through the scheduler.

The bearer token must contain at least 16 characters. Use a randomly generated credential. The configured URL must end at /v2/send, use HTTPS and resolve to an address reachable from Pharos; private networks are supported for your own bridge, but loopback and link-local destinations are blocked by Pharos's outbound request protection.

Troubleshooting

Check bridge account registration, the recipient, TLS and reverse-proxy authentication. Never publish the token in screenshots or support logs. A reachable bridge does not prove Signal delivery: confirm receipt on the device.