FAQ
Quick answers to the questions that come up most. For step-by-step walkthroughs, start at Getting started; for every endpoint, see the API reference.
How do alerts get into OpsPing?
Your monitoring tools POST them to the API. Create an integration in the console, copy the API key it generates, and send alerts to POST /v2/alerts using the OpsPingKey scheme. OpsPing acks with 202 and the alert lands in the list, ready to page whoever is on call. See Getting started for a working curl example.
We're moving from an end-of-life or legacy on-call tool. Do we have to rewrite our tooling?
No. OpsPing accepts the GenieKey scheme as an alias for OpsPingKey, so existing OpsGenie-compatible integrations keep posting without changes while you migrate. The Migration guide maps the concepts and APIs and walks through the cutover.
What's the difference between a responder and a stakeholder?
Responders are paged — they go on schedules, receive alerts, and can acknowledge, escalate, and resolve. Stakeholders are a free, non-paging tier: they follow status from the mobile app's Status tab and receive announcements, but they're never paged and don't see the paging-specific settings. See Teams & administration for role assignment.
How are notifications delivered, and what happens if I miss a page?
By push notification first, with optional SMS, voice, and email channels you verify per user — see Notifications & channels. If a P1 alert has no escalation policy and isn't acknowledged, OpsPing repings it — repeating the critical push every few minutes until someone acks, snoozes, or closes it.
What are critical alerts, and why do they need a physical device?
Critical alerts override iOS Focus / Do Not Disturb so an on-call P1 always makes noise. They require Apple's Critical Alerts entitlement and a physical device to test — simulators don't receive push. Setup is covered in Mobile setup.
Where are timestamps shown, and what timezone is used?
OpsPing stores every timestamp in UTC and respects the schedule's timezone for rotation math; the console and mobile app render times in your local timezone. You don't need to configure a timezone for display.
How do I give OpsPing support temporary access, safely?
Invite a dedicated support user for the duration of the issue, then delete it (or let the invite lapse) when you're done. Every action the support user takes is attributed to it and recorded in the audit log, so you can review exactly what happened. The full pattern is in Teams & administration.
Is each customer's data isolated?
Yes. OpsPing is multi-tenant with hard isolation between tenants — there is no admin bypass into another tenant's data. Users, teams, schedules, and alerts all scope to your tenant.