Adalo API
★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject Managementbearer6 EndpointsREST
For Agents
Read and write records in an Adalo app's collections and send push notifications to its users via the Adalo API.
Use for: I need to create a record in an Adalo collection, Update a user's profile in my no-code app, Delete an outdated record from a collection, Send a push notification to app users about an offer
Not supported: Does not handle visual UI editing, app publishing, or user authentication flows — use for Adalo collection CRUD and push notifications only.
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.
Install Jentic One Beta
Connect the Adalo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adalo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Adalo API.
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
Patterns agents use Adalo API for, with concrete tasks.
★ 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.
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.
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.
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 the Jentic vault, so the agent searches by intent — 'create a record', 'send a push' — without makers needing to handle raw keys.
Search Jentic for 'create an Adalo collection record', load the schema, and execute it with appId, collectionId, and field values
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for adalo api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adalo bearer tokens are stored encrypted in the Jentic vault per app. Agents receive scoped execution handles, so raw tokens never appear in prompt context, logs, or tool arguments.
Intent-based discovery
Agents search Jentic by intent, e.g. 'create an Adalo record' or 'send a push to Adalo users', and Jentic returns the matching operation with its input schema.
Time to first call
Direct Adalo integration: a few hours for auth, schema mapping, and notification flow. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Adalo API through Jentic.
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 at https://app.jentic.com/sign-up.
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 the Jentic vault 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.
GET STARTED