nitroping SDKs

Official client libraries for nitroping — one
platform to reach every device: push (iOS/APNs, Android/FCM, Web Push) plus
email, SMS, and Slack.

The SDKs wrap the REST API so you don’t hand-roll HTTP calls. Depending on the
language they let you:

• Register & manage device tokens (APNs / FCM / Web Push endpoints).
• Send & target notifications — to a device, a user, everyone, tags,
  rule-based segments, or a topic; now, scheduled, or recurring.
• Subscribe browsers to Web Push and drop in ready-made UI widgets (a
  permission prompt + an inbox bell) — JS only.
• Read the in-app inbox and report engagement / conversions.
• Verify webhooks (HMAC-SHA256), server-side.

Full guides + the interactive API reference: https://nitroping.dev/docs.

Pick your SDK

Quickstart

Server-side send with the JavaScript SDK:

npm i nitroping

import { Nitroping } from "nitroping"

const np = new Nitroping({ apiKey: "np_..." }) // secret key, server-side only

await np.notifications.send({
  target: { all: true },
  title: "Hello 👋",
  body: "Your first notification.",
})

Browser code uses a public pk_… key instead — see the
JS README for nitroping/web (subscribe to Web Push) and
nitroping/widgets (drop-in UI). Each language README has its own quickstart.

Wire-format reference

Every SDK speaks the same HTTP API. The canonical reference is the docs site:

• API: https://nitroping.dev/docs (interactive reference at /api/docs)
• Auth: Authorization: ApiKey np_… (secret, server) or
  Authorization: Public pk_… (public, browser/mobile-safe)
• Webhook signature: X-Nitroping-Signature: t=<unix>, v1=<hmac_sha256_hex>
  over <unix>.<raw_body>
• Idempotency: Idempotency-Key header on POST /api/v1/notifications

License

MIT — see LICENSE.

For maintainers

./bump.sh <X.Y.Z>            # bump VERSION + every manifest, commit, tag
git push origin main --follow-tags