Adalo API

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.