canonical: https://jentic.com/apis/adalo.com/adalo

# Adalo API

Jentic publishes the only available OpenAPI specification for Adalo API, keeping it validated and agent-ready. Adalo is a no-code app builder, and this API exposes external read and write access to the data collections that back an Adalo app, plus a push notification endpoint to message app users. The spec covers six operations under two tags: standard CRUD on collection records under /v0/apps/{appId}/collections/{collectionId} and a single push notification path. Authentication uses bearer tokens scoped per Adalo app.

## For AI agents

Read and write records in an Adalo app's collections and send push notifications to its users via the Adalo API.

## Scope

Does not handle visual UI editing, app publishing, or user authentication flows - use for Adalo collection CRUD and push notifications only.

## Capabilities

- List and create collection records under /v0/apps/{appId}/collections/{collectionId}
- Read, update, and delete a single record at /v0/apps/{appId}/collections/{collectionId}/{recordId}
- Send push notifications to app users via /notifications
- Scope access per app using app-specific bearer tokens
- Bridge an Adalo no-code app with external systems by reading or writing its underlying collection data

## Use cases

### External data sync to no-code apps

Operators of no-code apps often need to keep collection data in sync with an external CRM, spreadsheet, or analytics tool. An agent can list collection records via /v0/apps/{appId}/collections/{collectionId}, diff against the source of truth, and POST or PUT to add or update records. This avoids the manual CSV upload loop that no-code teams typically rely on.

Example prompt: Diff a Google Sheet against /v0/apps/{appId}/collections/{collectionId} and POST any new rows

### Event-driven push notifications

Adalo apps can push notifications to users via the /notifications endpoint. An agent watching an external system (e.g. an order status webhook) can fire a contextual push to the affected app user when something changes. This decouples the no-code app's UI from server-side events that would otherwise require custom backend code.

Example prompt: POST a push notification to /notifications when an order status changes, addressed to the affected app user

### Record lifecycle automation

Teams running no-code apps automate housekeeping - archiving old records, marking inactive users, or expiring promotional codes. An agent can list collection records, evaluate each record against a rule, and PUT or DELETE on /v0/apps/{appId}/collections/{collectionId}/{recordId}. This is the kind of janitor task no-code apps usually leave to manual edits in the Adalo UI.

Example prompt: List records older than 90 days in collection 5 and DELETE them via /v0/apps/{appId}/collections/{collectionId}/{recordId}

### AI agent integration

No-code app makers building agent assistants expose Adalo through Jentic alongside spreadsheet and email APIs. The bearer token lives in your Jentic One instance, so the agent searches by intent - 'create a record', 'send a push' - without makers needing to handle raw keys.

Example prompt: Search Jentic for 'create an Adalo collection record', load the schema, and execute it with appId, collectionId, and field values

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v0/apps/{appId}/collections/{collectionId} | List records in a collection |
| POST | /v0/apps/{appId}/collections/{collectionId} | Create a record |
| GET | /v0/apps/{appId}/collections/{collectionId}/{recordId} | Get a record |
| PUT | /v0/apps/{appId}/collections/{collectionId}/{recordId} | Update a record |
| DELETE | /v0/apps/{appId}/collections/{collectionId}/{recordId} | Delete a record |
| POST | /notifications | Send a push notification |

## Key resources

- **Collections** — Adalo app data collections - list, create, read, update, delete records
- **Notifications** — Send push notifications to app users

## Why Jentic

- **Setup:** Wiring the Adalo API by hand means holding its bearer token per app and threading the app id, collection id, and record id through every collection CRUD call. Through Jentic you install once, import the Adalo API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Adalo puts the app and collection ids in the URL path (/v0/apps/{appId}/collections/{collectionId}/...), so a rule can pin your agent to one collection: it can create and read records in that collection and nothing else. You choose the operations it may call, so deleting records or sending push notifications is not included unless you add it.
- **Credential handling:** Your Adalo bearer token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an Adalo record' or 'send a push to Adalo users', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Airtable API** — Spreadsheet-database hybrid often used as the data layer behind no-code tools.
- **Webflow API** — No-code site builder with CMS collections that mirror Adalo's collection idea for marketing sites.
- **Glide API** — Mobile-first no-code app builder with spreadsheet-backed data collections.

## FAQ

### Why is there no official OpenAPI spec for Adalo API?

Adalo publishes API documentation but not a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Adalo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Adalo API use?

Adalo uses HTTP bearer token authentication. Each Adalo app has its own API key issued from the app settings. Through Jentic, the bearer token is stored encrypted in your Jentic One instance and the agent receives a scoped execution handle, so the raw token never appears in the agent's context.

### Can I create and update records in Adalo collections via the API?

Yes. POST to /v0/apps/{appId}/collections/{collectionId} to create a record, GET/PUT/DELETE on /v0/apps/{appId}/collections/{collectionId}/{recordId} for the standard lifecycle. The fields available match the collection schema configured in your Adalo app.

### What are the rate limits for the Adalo API?

The OpenAPI spec does not declare explicit rate limits, so check Adalo's developer documentation for the current ceiling tied to your plan. Bulk record changes should be paced to avoid 429 responses.

### How do I send a push notification to Adalo app users through Jentic?

Run pip install jentic, search Jentic for 'send an Adalo push notification', load the schema for POST /notifications, and execute it with the audience and message body. Jentic injects the bearer token from the vault.

### Is the Adalo API free?

Adalo's API is gated by app plan - external API access is available on paid Adalo plans rather than the free tier. Check Adalo's pricing page for the specific tier required, then provision the API key from the app settings.

### Can I limit what my agent is allowed to do with the Adalo API?

Yes. Jentic One runs self-hosted, so your own rules decide which Adalo operations and which credential the agent may use. Because Adalo puts the app and collection ids in the URL path (/v0/apps/{appId}/collections/{collectionId}), you can pin the agent to a single collection and to a single app-scoped bearer token. You also choose the operations it may call, so you can allow listing and creating records while excluding record deletion or the /notifications push endpoint unless you add them.