FlowynBETA
LoginSign up

Request a URL on an interval and record what happened.

A name, method, URL, interval, and assertions go in. Check results with status and latency, plus incidents on repeated failure, come out.

Start building Read the docs
Checking every 60s
test
GETapi.example.com/health
Healthy
last 16 checks · interval 60slatest 184 ms
12 consecutive passing checks. Flowyn requests the URL, records status and latency, and does not touch your API.
What it does

Real product states, not a promise.

A name, method, URL, interval, and assertions go in. Check results with status and latency, plus incidents on repeated failure, come out.

  • Interval from 30 seconds to 24 hours
  • Status and latency per check
  • Incident after three consecutive failures
  • Recovery recorded on the next pass
Input

Name, method, URL, interval, and assertions

Output

Check results, latency, and incidents

Where it fits

Where it fits

01

Public API health

02

Customer-facing endpoints

03

An agent's HTTP endpoint

API example

One durable request.

POST /v1/monitors. Use an idempotency key on create calls. The full request and response contract is in Flowyn Docs.

POSThttps://api.flowyn.dev/v1/monitors201
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
      }
    ]
  }'
POST /v1/monitorsHeartbeatsPOST /v1/monitorsAPI checksGET /v1/issues/{fingerprint}Issues & diagnostics

Frequently asked questions

Where is the exact request contract for HTTP checks?
In Flowyn Docs and the OpenAPI document at https://api.flowyn.dev/openapi/v1.yaml. This page shows the request; the docs page lists every field, status value, error, and limit.
Is the operation durable?
Yes. The operation is stored before any work happens and remains a resource with state, attempts, and error context, not an ephemeral request log.
Do failures stay inspectable?
Yes. Every attempt is recorded. Repeated failures with the same fingerprint are also grouped into an Issue.

Build with HTTP checks.

Create a workspace, make your first call in the test environment, and inspect every attempt.

Start building Read the docs