SNPP (Pager)

Slug: pager_snpp
Provider: Simple Network Paging Protocol (RFC 1861)
Inbound ACK: No

---

How it works

PSAPLink connects directly to an SNPP server via TCP and sends a text message to a pager. SNPP is used for legacy alpha-numeric pager systems. The protocol is plaintext TCP — use only within a secured internal network or VPN.

---

Configuration schema

Field	Type	Required	Description
host	string	Yes	SNPP server hostname or IP address.
pager_id	string	Yes	Pager PIN or subscriber ID on the SNPP server.
port	integer	No	SNPP TCP port (default: 444).
timeout_seconds	integer	No	TCP connection timeout in seconds (default: 10).

---

Create a channel

POST /api/v1/transport-channels
Authorization: Bearer <token>
Content-Type: application/json

{
  "transport_type_slug": "pager_snpp",
  "name": "Supervisor Pager",
  "config": {
    "host": "pager.yourorg.local",
    "pager_id": "12345",
    "port": 444
  }
}

---

Test the channel

POST /api/v1/transport-channels/{id}/test
Authorization: Bearer <token>

---

Limitations

• No inbound ACK. Users must acknowledge via the PSAPLink web dashboard.
• SNPP is unencrypted. Do not route SNPP traffic over public networks without a VPN.
• Message length is truncated to 160 characters before sending.
• SNPP servers may impose rate limits or queue delays for high-volume sends.