Your data stays yours
API Builder runs on your own server. Nothing is copied out in bulk: an application with a key sees only the datasets that key allows, and a key can be withdrawn at any time.
API Builder puts an API on top of the database your old application already uses. No changes to the old system, no database port opened to the internet. You choose exactly what is shared, and with whom.
One package for Windows, Linux (deb, rpm incl. Oracle Linux 7), Docker and macOS, with the Installation Guide. No source code. Download the package · Installation guide
API Builder runs on your own server. Nothing is copied out in bulk: an application with a key sees only the datasets that key allows, and a key can be withdrawn at any time.
One program next to your database: a Windows service, a Linux package, a Docker container or macOS. Your legacy application is not touched.
Publish a dataset in a few clicks: the table, the columns, and a row filter if only part of it should be shared. Nothing else is visible.
Each partner or app gets its own API key with its own rights: read only or, only when you switch it on, insert, update and approved procedure calls.
Encrypted connections, and an optional relay so your server never needs an inbound port. Limit simultaneous connections per source so the old system is never overloaded.
No upgrade, no migration, no new database. API Builder speaks to the database your application already uses, even an Oracle version older than most APIs.
Every key comes with its own OpenAPI description, listing only the datasets and procedures that key may use.
A header and its lines in one call: later rows can use the id generated by an earlier one, and it all commits or nothing does.
Send an Idempotency-Key with any write. A retried request returns the first answer instead of creating a second record.
Download the package and the Installation Guide, or talk to us and we will set up the first datasets with you.