Service Level Agreement

Last updated: September 5, 2026

On this page 7 sections

This SLA applies to paid subscriptions provided by Parse API LLC, trading as ParseAPI. It describes what we aim to deliver and how credits work if we miss uptime targets. Free plans are best-effort and not covered here.

1. Covered service

"Service" means the public API at api.parseapi.com for documented endpoints and related health checks. Dashboard and billing are separate, outages there don't count against API uptime unless we say otherwise.

2. Uptime

We target 99.9% monthly uptime for the API, measured as successful responses (non-5xx) on core lookup routes, excluding scheduled maintenance we announce in advance.

Uptime is calculated per calendar month. If we don't hit 99.9%, eligible customers can request a service credit (see section 5). Pulse shows sampled health checks. Those samples are operational indicators, and do not replace the monthly measurement described here.

3. Latency

Published latency figures are regional median (p50) times to the first byte, measured against production from cities worldwide. Our Pulse page explains the measurements. We do not guarantee global p95 latency in this SLA. Regional performance varies with distance and routing.

4. Support

Email Email for account, billing, and API usage questions. We respond in the order requests arrive, regardless of plan. Response times vary and are not guaranteed.

5. Service credits

If monthly API uptime falls below 99.9% and you're on a paid plan, you may request a credit equal to 10% of that month's subscription fee for the affected ParseAPI product. Credits apply to future invoices, not cash refunds unless required by law.

To claim: email Email within 30 days after the month ends, with the dates/times you saw failures. We'll verify against our logs and apply credits if the SLA was missed.

6. Exclusions

This SLA doesn't apply when downtime or errors are caused by:

  • Free-tier usage
  • Scheduled maintenance (with reasonable notice when we can give it)
  • Your misconfiguration, invalid keys, or client-side bugs
  • Abuse, rate overload, or attacks aimed at your keys or our infrastructure
  • Third-party outages (DNS, cloud providers, payment processors, etc.)
  • Force majeure (natural disaster, war, widespread internet failure, etc.)
  • Beta features, undocumented routes, or endpoints we've marked as unavailable

7. Changes

We may update this SLA. The date at the top changes when we do. Material changes won't reduce credits for an already-paid month retroactively.

Part of your paid subscription under our Terms of Service. Questions about this SLA: Email.