Durable HTTP
Make any HTTP call survive timeouts, 503s, and deploys.
Hand Flowyn the request. It is stored first, retried within a finite policy, and finished with a history you can read.
- Stored before execution, retried with backoff
- Every attempt kept with status and latency
- Cron schedules that create the same durable jobs
Starter · $0 · 10,000 credits a month · no card
test
POSThttps://api.example.com/reports/generate
Queued- job
- job_8f29a
- policy
- 5 attempts · exp. backoff
- timeout
- 10,000 ms
- idempotency
- sync-invoice-881
Attempts · append-only
The call is persisted before any worker runs it. Nothing has been sent yet.
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/jobs202
curl -X POST https://api.flowyn.dev/v1/jobs \
-H "Authorization: Bearer flw_test_••••" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: sync-invoice-881" \
-d '{
"url": "https://api.example.com/reports/generate",
"method": "POST",
"timeout_ms": 10000,
"max_attempts": 5
}'Quick answers
Is execution exactly once?
No. At-least-once. Every attempt carries Idempotency-Key set to the job id so the destination can deduplicate.
Can I cancel?
Yes, before the job finishes. Attempts already made stay in history.
What does it cost to start?
Starter is $0 with 10,000 credits a month. Paid plans start at $9/month.
