Configure a destination and test it.
A configured HTTPS destination goes in. A test delivery with its recorded result comes out. The signing secret is shown only once, at creation.
test
order.completed
evt_8e12c · signed · idempotency order-123
https://hooks.example.com/orders
Delivery attempts
Persisted before any endpoint is called. Your request already returned HTTP 202.
What it does
Real product states, not a promise.
A configured HTTPS destination goes in. A test delivery with its recorded result comes out. The signing secret is shown only once, at creation.
- Signing secret revealed once
- Test delivery with recorded HTTP status
- Disable without deleting history
- Rotate the signing secret
Input
A configured HTTPS destination
Output
A test delivery with its result
Where it fits
Where it fits
01
Connecting a partner system
02
Validating a new receiver
03
Staging before live
API example
One durable request.
POST /v1/endpoints/{id}/test. The full request and response contract is in Flowyn Docs.
AcceptedClaimedAttemptedTerminal statePOSThttps://api.flowyn.dev/v1/endpoints/{id}/test202
curl -X POST https://api.flowyn.dev/v1/endpoints/{id}/test \
-H "Authorization: Bearer flw_test_••••" \
-H "Content-Type: application/json"Frequently asked questions
Where is the exact request contract for Integrations?
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 Integrations.
Create a workspace, make your first call in the test environment, and inspect every attempt.