Openness
What comes in, what goes out, and through where
Rondea does not claim to replace your information system: it sits beside it. Everything the console does goes through a public API, and everything that happens can be pushed to you.
15 days • 10 users • no card required
The API
One API, the one the console uses
There is no impoverished public API beside a complete internal one. Routes are described in OpenAPI, and the description is generated from the code that validates requests — so it cannot lie.
- Scoped keys
- A read key for your data warehouse, a write key for your ERP. Each can do only what it is for, with its own call limit.
- Readable errors
- Errors follow a standard shape: a type, a title, a detail. Your integration knows why it was refused without parsing an HTML page.
- Forms too
- Create a form, upload a draft, publish a version, open access to a group: administration is drivable, not just reading.
Webhooks
Receive what happens here, on your side
A subscription, an address, a secret. Every delivery is signed, logged, and retried if it fails.
- Signed
- A digest computed with your secret accompanies every delivery: your server checks the call really came from us.
- Retried, with a log
- A missed delivery goes again, and the log says what was attempted and why it failed. You do not learn about the outage from a hole in your data.
- Refused inwards
- A private, loopback or link-local address is refused. Without that, a customer could use our servers to reach their own internal network.
In and out
Both directions matter equally
Taking over what you are leaving and being able to leave with everything are not decorative features: they are the two moments where a vendor shows what it thinks of its customers.
- Kizeo form import
- With a field-by-field report: what was taken as is, what was converted, what needs a decision.
- History import
- CSV and Excel, validated line by line, with the detail of refused lines and why.
- Export of everything
- Submissions, media, form definitions. Nothing stays captive in a format you could not read elsewhere.
What does not exist yet
No off-the-shelf third-party connectors
There is no Zapier connector, no SharePoint connector and no ERP connector in the product today. That would be easy to imply with a wall of logos; it is not the case, and saving you the discovery after signature is the point.
- What exists instead
- The API and webhooks cover the same uses, with a little code on the integrator's side. That is less comfortable than a connector, and it is honest.
- What will come
- Connectors need partner accounts and validation by the vendors concerned. They will be announced when they work, not before.
- What you can ask for
- If your integration hits a missing route, write to us: the API is young, and its gaps close quickly once named.
Is the API limited by plan?
Call limits are set per key. The detail is on the pricing page and in the API documentation.
Is the documentation up to date?
It is generated from the code that validates requests, and a test fails if repository and documentation diverge. A route therefore cannot exist without appearing in it.
Plug it into what you already run
A read key, a webhook, and your data warehouse receives the field's submissions the same evening.