?php
// Page: uptime-api
return [
'meta.uptime-api.title' => 'API Monitoring Service',
'meta.uptime-api.description' => 'API monitoring service that validates response bodies, not just status codes. Assert on JSON field values, response time SLAs, and cert expiry — with instant alerts when assertions fail.',
'uptime-api.hero.eyebrow' => '[ UPTIME MONITORING ]',
'uptime-api.hero.h1' => 'API Monitoring Service',
'uptime-api.hero.sub' => 'Status 200 does not mean your API is working. Our API monitoring service checks what your endpoints actually return — validating JSON field values, asserting response time SLAs, and tracking TLS certificate expiry. Get alerted the moment an assertion fails, not when a customer reports a broken integration.',
'uptime-api.parent' => 'Uptime Monitoring',
'uptime-api.diff.h2' => 'Beyond Ping: API Monitoring That Validates What Matters',
'uptime-api.diff.p1' => 'Basic uptime monitoring checks whether your endpoint returns a 200 status code. But a 200 response can still mean your API is broken — returning an empty array where a populated list is expected, a null where a required ID should appear, or a response time of 8 seconds when your SLA promises 500ms. Customers experience the failure; your uptime dashboard stays green.',
'uptime-api.diff.p2' => 'Our API monitoring service goes beyond reachability to validate correctness. Define assertions on specific JSON fields, response time thresholds, expected status codes, and certificate expiry windows. Each check runs on your configured schedule and fires an alert the moment any assertion fails — with the actual response body included so you can diagnose immediately without reproducing the issue.',
'uptime-api.inc.label' => 'WHAT\'S INCLUDED',
'uptime-api.inc.h2' => 'HTTP Monitoring That Checks Correctness, Not Just Reachability',
'uptime-api.inc.endpoint-monitoring.h3' => 'Endpoint Monitoring',
'uptime-api.inc.endpoint-monitoring.p' => 'Monitor REST, GraphQL, and webhook endpoints on any schedule from 1 minute upwards. Supports GET, POST, PUT, and DELETE methods with custom headers and request bodies. Authentication via Bearer token, Basic auth, or custom header.',
'uptime-api.inc.body-validation.h3' => 'Response Body Validation',
'uptime-api.inc.body-validation.p' => 'Assert on JSON field values using JSONPath expressions — check that a field exists, equals an expected value, or matches a pattern. Catch silent data failures that a status-code check completely misses.',
'uptime-api.inc.alerts.h3' => 'Multi-Channel Alerts',
'uptime-api.inc.alerts.p' => 'Alerts fire via email, Slack, or PagerDuty the moment an assertion fails. Each alert includes the endpoint URL, the failed assertion, the actual response body, and the response time — enough context to diagnose without opening a separate tool.',
'uptime-api.inc.reporting.h3' => 'SLA Reporting',
'uptime-api.inc.reporting.p' => 'Per-endpoint uptime percentages, average response times, and p95/p99 latency over 24h, 7d, 30d, and 90d windows. Exportable for SLA reviews, customer commitments, and compliance audits.',
'uptime-api.faq.h2' => 'Frequently asked questions',
'uptime-api.faq.q1' => 'What is API monitoring?',
'uptime-api.faq.a1' => 'API monitoring is the continuous testing of your HTTP endpoints to verify they are reachable, responding correctly, and meeting performance SLAs. Unlike basic uptime monitoring that only checks whether a URL returns any response, API monitoring validates what the response contains — asserting on specific JSON fields, status codes, response time thresholds, and certificate validity. It catches silent failures that a green uptime dashboard completely misses.',
'uptime-api.faq.q2' => 'How often do you check APIs?',
'uptime-api.faq.a2' => 'Check intervals are configurable per endpoint: 1 minute, 5 minutes, 15 minutes, or 60 minutes. Most API monitors run on a 1- or 5-minute schedule. Before alerting, we confirm the failure across multiple consecutive checks to eliminate false positives from transient network blips. You choose the balance between detection speed and alert noise.',
'uptime-api.faq.q3' => 'What alerts do you send when an API check fails?',
'uptime-api.faq.a3' => 'When an assertion fails, you receive an alert via your chosen channel (email, Slack, PagerDuty) containing: the endpoint URL, which assertion failed (e.g. “response.data.id was null, expected integer”), the full response body, the HTTP status code, and the response time. A recovery alert fires when the endpoint passes all assertions again, including the total outage duration. No manual acknowledgement required — the recovery closes the incident automatically.',
'uptime-api.faq.q4' => 'How is API monitoring different from uptime monitoring?',
'uptime-api.faq.a4' => 'Uptime monitoring checks reachability: is the URL responding at all? API monitoring checks correctness: is the response what your application expects? An API endpoint can be fully reachable (200 status, fast response) while returning broken data — an empty list, a missing field, a stale cache hit. API monitoring catches these silent failures. We include both in our platform: uptime monitoring for infrastructure health, API monitoring for integration correctness.',
'uptime-api.cta.h2' => 'Start Monitoring Your APIs in Under 5 Minutes',
'uptime-api.cta.sub' => 'Add your first endpoint, define your assertions, save — we start checking immediately. No agents, no infrastructure changes, no code required.',
];