Lovable API
Manage and deploy your Lovable projects and read workspace data from agent work.
Connect it with: API key. Lovable API's own documentation: https://docs.lovable.dev/features/api-keys.
What agents can do
Connect Lovable API so the agents working your tasks can reach it. With it connected, they can:
- List the workspace's projects and read their settings and status.
- Deploy or publish an existing Lovable project from a task.
- Read workspace members, groups, security insights and analytics for a report.
Before you start
- A Lovable workspace on the Business or Enterprise plan, and the Owner or Admin role in it.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Lovable API
Jaah connects to Lovable API with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- API key: Lovable > Workspace settings > API keys & OAuth > Workspace access tokens > New API key: name it Jaah, choose access for Projects and Workspace (Read for a read-only connection), then Create and copy it - Lovable shows it once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Lovable API card.
- Name the secret and choose who can use it.
- Fill in API key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Lovable API with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Lovable API with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: api_key.
Tell the agent in your task description which secret to use, for example “use the Lovable API secret org/lovable”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Lovable API once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Lovable API's side too, revoke or delete the key at Lovable API.
Limitations
- A key reaches one workspace; connect each workspace separately.
- The API manages and deploys existing projects; it does not build or edit apps with Lovable's AI.
- A key with an IP allowlist refuses calls from other addresses with 403 ip_restricted: leave the allowlist empty, or add the addresses your Jaah calls from.
- Agents can do only what the connected Lovable API account allows.
Troubleshooting
Test says Lovable rejected the API key
The key was revoked or mistyped. Create a new key in Workspace settings > API keys & OAuth and select Replace.
Test fails with 403 ip_restricted
The key's IP allowlist does not include Jaah. Clear the allowlist or add Jaah's outbound addresses.
There is no API keys option in Workspace settings
The workspace is not on Business or Enterprise, or you are not an Owner or Admin.
Still stuck? Select Test and read the result: it names the value Lovable API refused and the status it answered.
FAQ
Does the API use my AI credits?
No. Lovable's current API endpoints do not consume AI build credits.
Which access should the key have?
Read on Projects and Workspace for a look-only connection; Read & write on Projects to let agents deploy.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Lovable API account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.