API monitoring
Know the moment your API or cron job stops working.
HTTP checks, heartbeats for scheduled jobs, and API assertions. Failures open incidents, recovery is recorded, repeated errors become one issue.
- Checks as often as every 30 seconds, with latency history
- Heartbeats catch cron jobs that silently stop
- Incidents with evidence, closed on recovery
Starter · $0 · 10,000 credits a month · no card
test
GETapi.example.com/health
Healthylast 16 checks · interval 60slatest 184 ms
12 consecutive passing checks. Flowyn requests the URL, records status and latency, and does not touch your API.
The API call
This is the whole integration.
One request with your API key and an Idempotency-Key. Flowyn returns an id; read the result whenever you like. Full product details.
POSThttps://api.flowyn.dev/v1/monitors202
curl -X POST https://api.flowyn.dev/v1/monitors \
-H "Authorization: Bearer flw_test_••••" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: monitor-prod-health" \
-d '{
"name": "Production API",
"type": "http",
"method": "GET",
"url": "https://api.example.com/health",
"interval_seconds": 60,
"timeout_ms": 5000,
"assertions": [
{
"source": "status_code",
"operator": "equals",
"expected": 200
}
]
}'Quick answers
Does Flowyn fix my API?
No. Flowyn observes and reports facts. It opens an incident and tells you; it does not change your system.
How do heartbeats work?
Your job pings Flowyn after each run. If no ping arrives within twice the interval it is recorded as missed, and three misses in a row open an incident.
What does it cost to start?
Starter is $0 with 10,000 credits a month. Paid plans start at $9/month.