PingLoom docs

Send events from your server. Your team sees them in a shared inbox on their phones and in the dashboard.

What PingLoom does

Your server calls one endpoint with a project API key. PingLoom stores the event first, then sends a minimal push through Google FCM to the phones of the people who follow that channel. The full message is fetched by the app after sign-in, so the push itself carries no body.

The PingLoom app for Android and iOS is in private testing. It isn't on Google Play or the App Store yet.

Where to start

• Quickstart: create a project, get a key and send your first alert in five steps.
• API reference: fields, limits, headers, errors and the status endpoint.
• Status codes: what each status and delivery state means.
• Python SDK, Node SDK, command line tool and GitHub Action: send from the places you already work.

How it works

1. You send POST /v1/notifications. PingLoom answers 202 once the event is stored.
2. A background worker finds the people who follow the channel and prepares one send per active device.
3. FCM accepts or rejects each send. PingLoom shows exactly that, and which devices have seen the event.

Your first 20 test events from the dashboard don't count toward your quota. PingLoom confirms what FCM accepted and what the app reported. It cannot confirm that a phone showed an alert.