Payment API unavailableCheckout service
NewSimple paging for people who need to act
One app. Two ways to reach the right people.
Use Sevloom as a managed paging service for your systems, or create a personal circle for direct app-to-app paging with family and friends.
Start with the experience that fits: connect an API, or connect people directly.
Monitoring signalTrusted relaySevloom pageHuman response
Choose how you page
Choose the path that fits how you need to page.
Every Sevloom experience uses the mobile app to receive and acknowledge pages. Choose whether pages come from your backend or directly from another paired app.
Managed paging
For teams and applications
Download and pair the Sevloom app on responder devices, then send structured pages from your backend through the Sevloom API.
See the API guidePersonal paging
For family and friends
Download the Sevloom app, create a personal circle, connect devices directly, and send urgent messages without a dashboard or API key.
Download and set upWhat Sevloom does
Connect your systems to the people who need to respond.
Your applications and monitoring tools can send pages to Sevloom through the API. Personal circles can send pages directly between paired apps. Sevloom handles delivery and acknowledgement while your systems continue to generate events the way they already do.
Send from where the event happens
Send a page from an API, application, monitoring workflow, or another paired app when a person needs to respond.
Choose who receives it
Route pages to managed responder devices or directly to the people connected to a personal circle.
Give responders enough context
Include urgency, source, message, and supporting details so the recipient knows what needs attention.
Inside the app
Designed to reduce the distance between an alert and a decision.
Production
New page
Delivery queue requires attention
Queue depth has remained above the configured threshold for five minutes.
Triggered · Just now
AcknowledgeResolve
Pages that stay legible
A compact page list makes severity, source, environment, and lifecycle status easy to scan—without turning your phone into another dashboard.
A deliberate lifecycle
Acknowledge when you are on it. Resolve when the condition is addressed. Reopen when the same incident needs attention again.
Paging sounds by severity
Use distinct pager tones for SEV-1 and SEV-2 pages, with normal system sounds for SEV-3 through SEV-5 when enabled.
Privacy-minded configuration
The app keeps each environment separate. Integration API keys belong in trusted server-side code, never in the mobile app or a browser.
The mobile app
The place where pages reach people.
Use Sevloom on the devices people carry to receive, understand, and acknowledge important pages—whether they come from a connected system or another circle.
A portable integration model
One event shape. Many sources.
The hosted API accepts a consistent HTTPS page request. Applications, cloud alarms, and monitoring tools can map their signals to the same public contract.
The API guide explains the request format, authentication model, response shape, and error handling.
View the API contractpage eventv1
severitysev1 | sev2 | sev3 | sev4 | sev5environmentproduction | staging | customdeduplicationKeystable identifier for the active incidentsourcemonitor, service, or person that created the pageDesigned to be portable
Use your tools. Keep your choices.
The public integration contract is designed for monitoring platforms, cloud events, workflows, and custom applications. The mobile app source is available separately for developers who want to inspect, adapt, or contribute to the client.