⚡Notiboltdocs

Getting started

Notibolt is push notification infrastructure for iOS and Android that delivers through credentials you own — your APNs key and your Firebase service account. This guide takes you from zero to your first push in about ten minutes.

1. Create an app

Sign up at app.notibolt.com, create an organization and an app. Every app has two credentials:

CredentialUsed bySecrecy
App IDMobile SDKs (device registration)Public — safe to ship in your app
REST API key (nb_…)Your backend (sending notifications)Secret — server-side only

2. Upload your push credentials

In the panel, open App → Settings:

  • iOS: paste your APNs key (.p8), Key ID, Team ID and Bundle ID. Apple Developer → Certificates, Identifiers & Profiles → Keys → create a key with APNs enabled. Enable Use APNs sandbox for development builds.
  • Android: paste your Firebase service account JSON. Firebase console → Project settings → Service accounts → Generate new private key.
Credentials are stored encrypted (AES-256-GCM) and are only used to talk to Apple and Google on your behalf. You can rotate or remove them anytime.

3. Integrate an SDK

Follow the platform guide — each is a one-line init plus system callbacks:

Devices register themselves on first launch and appear in the panel under Devices with model, locale, timezone and permission status.

4. Send your first notification

From the panel (Send notification) or with one call from your backend:

curl -X POST https://api.notibolt.com/api/v1/apps/APP_ID/notifications \
  -H "Authorization: Key nb_your_rest_key" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Order shipped 📦",
    "body": "Arrives Thursday",
    "url": "myapp://orders/1234",
    "segment": { "tags": { "plan": "pro" } }
  }'

Watch targeted / sent / delivered / failed / opened update live in the panel. See the REST API reference for segmentation, scheduling, localization and more.

Core concepts

ConceptDescription
OrganizationTeam & billing boundary; holds apps and members.
AppOne mobile product with its own credentials and devices.
DeviceA subscribed installation — can carry an externalUserId and tags for targeting.
NotificationOne send request; fans out to matching devices via APNs/FCM.
DeliveryPer-device record: PENDING → SENT / FAILED → OPENED with error reasons.

Source code