Acked documentation

Set up paging, connect monitoring sources, and run your on-call response.

1. ServiceChoose what you monitor. 2. ScheduleChoose who responds. 3. PhoneEnable notifications. 4. TestConfirm the paging path. 5. SourceConnect monitoring.

Start with a working page

The fastest path to value is one alert that reaches the correct phone. Complete that path before you add more services, people, or automation.

Set up AckedCreate the first service and confirm a phone notification. Connect monitoringChoose a source for Datadog, Grafana, Alertmanager, PagerDuty, email, or JSON.

Operate your on-call response

Manage alertsAcknowledge, resolve, snooze, escalate, and add responders. Manage servicesRoute each monitored system to the correct schedule. Build schedulesCreate rotations, escalation levels, and temporary overrides. Manage your teamInvite members, assign roles, and protect account access. Set up mobile appsEnable notifications, verify device readiness, and prepare for voice paging. Review historyRead alert timelines, delivery attempts, and organization activity. Manage billingChoose a plan, manage payment details, and enable voice paging.

Understand Sources and Destinations

A Source sends signals into Acked. Direct sources target one service. Central vendor connections route payload attributes across services and use a fallback when no rule matches.

A Destination sends alert events out of Acked. Destinations are optional. Use them when another system needs lifecycle updates.

SourcesMonitoring tools, email, and custom senders. DestinationsSlack channels and signed HTTPS webhooks.

Build with Acked

Use the alert API for direct HTTP senders. Use a full product API key or MCP for trusted configuration automation.

Alert APIIntegration URLs, payloads, deduplication, and recovery. API keysAccess levels, storage, rotation, and revocation. HTTP API and OpenAPISchemas, receipts, webhook templates, and TypeScript examples. MCPInteractive OAuth for Codex and other AI agents. Product conceptsThe complete routing model and alert states.

Find and fix a delivery problem

Start with the alert timeline. It separates ingest, routing, provider delivery, and device display into distinct checks.

Follow the delivery troubleshooting guide.