The platform

Every feature, explained.
What it does, why it pays, how to use it.

No marketing fluff — here's exactly what you get and what it's worth to your business.

Core

Uptime & response monitoring

Your API is your product's front door. Apitinel knocks on it every few minutes — or every 30 seconds on Agency — and records whether it answered, how fast, and with what content.

Why it matters to your business

  • Downtime is revenue loss. If your checkout API 500s for 40 minutes at 2am, that's sales you'll never get back. We catch it in the first minute.
  • Slow is the new down. Response-time trends reveal degradation weeks before a full outage — fix it before customers churn.
  • Assertions, not vibes. Check status codes AND response content ("does the JSON actually contain status:"ok"?"), so a healthy-looking 200 that returns garbage still alerts you.

How to use it

  1. Click New Request → paste your endpoint URL
  2. Set method, headers, auth and (optionally) a request body
  3. Add assertions: expected status, required content, max response time
  4. Pick an interval — done. The sentinel is on watch.
POST /api/checkout 200 · 184ms
Intervalevery 60s
Assertionstatus = 200
Assertionbody contains "success"
Max time2000 ms
1,440 checks passed today
Core

Alerts that actually reach you

An alert you don't see is worse than no alert — it gives false confidence. Apitinel pushes to the channels your team lives in: email by default, Slack and Discord via native webhooks.

Why it matters to your business

  • MTTR is money. Every minute between "broke" and "someone noticed" costs customers. Direct-to-Slack alerts cut that to seconds.
  • No alert storms. Failure thresholds mean you hear about sustained problems, not single flaky seconds. Recovery notifications tell you when it's safe to go back to sleep.
  • Right channel, right people. Ops on Slack, the client-success team on email — everyone gets what they need.

How to use it

  1. Settings → add a Slack or Discord webhook URL (30 seconds)
  2. Choose which events notify: failures, recoveries, SSL warnings
  3. Set failure thresholds per monitor — sensitive for checkout, relaxed for a blog API
🔴 /api/checkout is DOWN
3 consecutive failures · HTTP 502 · last OK 2 min ago
🟢 /api/checkout recovered
Back to 200 in 141ms · downtime: 6 minutes
Trust

Public status pages & incident subscriptions

One toggle turns your monitors into a polished, public status page — your logo, your colors, your monitors. Customers subscribe to incident updates and get emailed automatically when something breaks and when it's fixed.

Why it matters to your business

  • Fewer support tickets. "Is it down or is it me?" is the #1 avoidable ticket. A status page answers it before they ask.
  • Transparency sells. Enterprise buyers check status pages during evaluation. A clean 90-day uptime history closes deals.
  • Controlled narrative. An outage you communicate is a hiccup. An outage customers discover is a betrayal.

How to use it

  1. Status Page → mark monitors as public, pick a slug
  2. Optionally upload your logo and brand colors (Pro+)
  3. Share the link in your footer and support docs — subscribers get incident emails automatically
All Systems Operational 100% · 24h
APIOperational
DashboardOperational
WebhooksDegraded
47 subscribers notified automatically
Trust

Embeddable uptime badges

A tiny SVG that shows your live uptime — in your GitHub README, your docs, your footer. Generated on the fly for 24h, 7-day, 30-day or 90-day windows.

Why it matters to your business

  • Instant credibility. "99.98% uptime" is a claim. A live badge that updates itself is proof.
  • Zero maintenance. Paste one <img> tag once — it stays accurate forever.
  • Dev-tool marketing. If you sell to developers, badges in your README are table stakes.

How to use it

  1. Mark a monitor public on your status page
  2. Grab the badge URL: /badge.php?id=…&period=30d
  3. Drop it in any HTML or Markdown — done
uptime 30d99.98% uptime 7d100% api statusoperational
<img src="https://app.apitinel.com/badge.php?id=1&period=30d">
Proof

Historical charts, SLA reports & weekly summaries

90-day uptime bars per monitor, response-time trends, a failure heatmap that shows when things break, and a weekly email summarizing it all. Your reliability, as data.

Why it matters to your business

  • SLA conversations need receipts. When a client claims "you're always down", a 90-day chart ends the argument in seconds.
  • Patterns prevent fires. The heatmap reveals "every deploy day at 15:00" problems you didn't know you had.
  • Weekly reports keep everyone honest — including your hosting provider.

How to use it

  1. Performance page → pick 7, 30 or 90 days
  2. Enable the weekly email report in Settings — it just arrives every Monday
  3. Export or screenshot charts straight into client reports
90-day uptime 99.55% avg
Weekly report: every Monday, 08:00, your inbox
Power

Multi-step scenarios

Real user journeys are chains: log in → create resource → verify it exists → clean up. Apitinel scenarios run exactly that, passing data between steps, and alert you if any link in the chain breaks.

Why it matters to your business

  • 200 OK on /login doesn't mean login works. Only a full flow proves the feature.
  • Catch integration rot. Third-party auth, payment gateways, webhooks — chains fail at the joints, not the endpoints.
  • Test like a user, alert like a machine. If step 3 of your onboarding flow breaks, you know before the first support ticket.

How to use it

  1. Create a scenario → add your existing requests as steps
  2. Extract values from responses (tokens, IDs) and reuse them in later steps
  3. Schedule it like any monitor — get alerted with the exact failing step
1 POST /auth/login 200
2 POST /projects 201
3 GET /projects/{id} 200
4 DELETE /projects/{id} 500
Alert: scenario failed at step 4 — cleanup broken
Silent killer

SSL certificate monitoring

Expired certificates take down more sites than server crashes. Apitinel tracks expiry dates for all your domains and warns you 30, 14 and 7 days out — on every channel.

Why it matters to your business

  • An expired cert is a full outage — with a scary browser warning that torches user trust instantly.
  • Auto-renew fails silently. Let's Encrypt cron jobs break all the time. We notice when they don't renew.
  • Agencies: one forgotten client cert renewal costs you the client. This is the cheapest insurance you'll ever buy.

How to use it

  1. SSL Certs → add a domain
  2. That's it — expiry checks run daily, warnings go to your alert channels
api.yoursaas.com82 days left
client-shop.com13 days left
old-blog.io2 days left
Warnings at 30 / 14 / 7 days — email + Slack
Sanity

Maintenance windows

Deploying at 3am? Schedule a maintenance window and Apitinel pauses alerts for exactly that period — checks keep running, history stays clean, nobody gets paged for planned work.

Why it matters to your business

  • Alert fatigue kills monitoring. If every deploy fires 12 false alarms, people start ignoring real ones.
  • Clean SLA math. Planned maintenance doesn't count against your uptime numbers.

How to use it

  1. Maintenance → New window → pick monitors and time range
  2. Deploy in peace — alerts resume automatically when the window ends
v2.4 deploy window
Monitorsapi, webhooks
Window03:00 – 03:30 UTC
Alerts paused · checks still recording
Organization

Collections, environments & scheduling

Group monitors by product, client or team. Store per-environment variables (dev / staging / prod URLs, tokens) and flip the whole collection between them. Run collections on schedules for batch health checks.

Why it matters to your business

  • Agencies: one collection per client — instant portfolio view, clean per-client status pages.
  • Staging vs prod in one click. Verify a release on staging, flip to prod, done.
  • Scale without chaos. 200 monitors stay findable, filterable and grouped.

How to use it

  1. Collections → New → drag monitors in
  2. Environments → define {{base_url}} per environment, use it in requests
  3. Scheduled → run a whole collection every hour, on a cron, whatever fits
Client: Acme Corp 12/12 passing
envbase_url = https://api.acme.com
scheduleevery hour
One click: staging ⇄ production

See it on your own endpoints.

Free plan: 3 monitors, email alerts, 7-day history. Set up in two minutes.

Start monitoring free