ºÚÁÏÕýÄÜÁ¿

Today, we are launching one of our most requested features - our new public API!

When you sign up for ºÚÁÏÕýÄÜÁ¿, you get a low-code platform with an internal database, external data connectors (MySQL, PostgreSQL, MSSQL, Oracle DB, Airtable, MongoDB…), user management, free SSO, drag and drop GUI for building UIs, powerful prebuilt components, free SSO, an automation interface (like Zapier) and now a flexible public API to interact with.

These services integrate very well with each other making the experience of building CRUD apps easier, faster, and a lot more flexible.

As with anything that we build in ºÚÁÏÕýÄÜÁ¿, our new public API is simple to use, flexible, and introduces new extensibility. To summarize, the ºÚÁÏÕýÄÜÁ¿ API enables:

1. ºÚÁÏÕýÄÜÁ¿ as a backend
   The ºÚÁÏÕýÄÜÁ¿ backend is very powerful, and our Public API allows you to specifically use the backend API to build apps, without using, for example, our design GUI. A common use case would be to pair the ºÚÁÏÕýÄÜÁ¿ backend with Grafana to build powerful dashboards, or to use ºÚÁÏÕýÄÜÁ¿ with a frontend framework . The number of potential use cases are vast.
2. Extending apps
   Right now users are limited to what you can do within ºÚÁÏÕýÄÜÁ¿. This can make it difficult to extend functionality in a lot of places, especially around data. The new ºÚÁÏÕýÄÜÁ¿ API allows users to build to a point within ºÚÁÏÕýÄÜÁ¿ and then extend using the API. This is only the beginning, as ºÚÁÏÕýÄÜÁ¿ continues to grow we will improve and expand the capabilities of our API.
3. Inter-operability
   Again right now for inter-op within an organization, you’re limited to what ºÚÁÏÕýÄÜÁ¿ can connect to. Opening up the API allows connecting data in and out of ºÚÁÏÕýÄÜÁ¿ in ways that are business-specific use cases (e.g. IoT, internal business APIs, etc).

Design

The API follows RESTful patterns of design and is fully defined using the OpenAPI specification. For schemas and API definitions this enables the spec to be pulled into tools like Postman and you can start making requests straight away once you’ve inputted your API key and App ID.

The first version of the API covers the tables, rows, users, queries, and applications resources. You have full CRUD operations on those resources as well as the ability to search any of them. This also respects the RBAC system fully. Every user can generate an API key for ºÚÁÏÕýÄÜÁ¿ and it will only allow users with access to resources to utilize the API.

Use case

To help you adopt the ºÚÁÏÕýÄÜÁ¿ API, we’ve created the following example:

1. Build an app with ºÚÁÏÕýÄÜÁ¿ and Next.js

Docs

You can learn more about the ºÚÁÏÕýÄÜÁ¿ API at the following places:

1. : Learn how to get your API key, how to use spec, and how to use with Postman
2. : Learn how to interact with the API