https://api.lovable.dev), using a workspace API key that a Lovable owner or admin creates. ConfigView sends only GET requests. It never creates, changes, publishes or deletes anything in Lovable.
You will end up with 1 required secret (LOVABLE_API_KEY) in ConfigView when setup is complete.
Scope of this integration today. ConfigView reads who is in your Lovable workspace (name, work email, role, whether your identity provider provisioned them through SCIM), the groups, every project with its visibility, publish audience, owner, created and last-edited dates, who collaborates on each project, the Security Center roll-up and per-project review priority (with the host a project is published at and the services it connects to), and daily workspace traffic totals. It does not read project code, prompts, chat messages, project descriptions, screenshots, security scan details or audit logs.
What you need
- A Lovable workspace on the Business or Enterprise plan. Free and Pro workspaces cannot create workspace API keys (Lovable answers 402 and shows an upgrade prompt).
- A Lovable owner or admin with a verified email, to create the key.
- One key per workspace. A key is bound to a single workspace; if you have several, create a key for each.
- If your workspace requires an IP allowlist on every key, or you restrict this key to an allowlist, ConfigView’s outbound IP address must be on it (see Step 2).
Step 1: Open the Lovable page in ConfigView
Open ConfigView in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/lovable
Step 2: Create the API key
- In Lovable open Workspace settings > API keys & OAuth > Workspace access tokens and create a new key
- Name it (for example
ConfigView) - Click Apply preset > Read only. ConfigView only needs
workspaces:read(the read-only preset also grantsprojects:read); never give it a:writescope. - Choose an expiry. Lovable offers 7, 30, 60, 90, 180 days, 1 year or never. A key that expires stops the collectors until you paste a new one, so set a calendar reminder.
- IP allowlist. Leave it empty if your workspace allows that. If you add one, include ConfigView’s outbound IPv4 address (Lovable’s API answers over IPv4 only). If the workspace requires an allowlist on every key, you must add one or the key is refused with
403 ip_allowlist_required. - Copy the
lov_key now. Lovable shows it once. - In the ConfigView tab paste it into
LOVABLE_API_KEYunder Credentials and save
Step 3: Connect and verify
- Click Connect. ConfigView creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the secret, then reads the workspace and one page of members.
- 401. The key is wrong, revoked or expired.
- 402. The workspace is not on the Business or Enterprise plan.
- 403. The key is missing a scope, or ConfigView’s IP address is not on the key’s allowlist (
ip_restricted,ip_allowlist_required).
Data Tables
Each table has arun_at column and keeps only the newest run.
Things worth knowing
Business or Enterprise only. Workspace API keys, and every endpoint ConfigView reads, require the Business or Enterprise plan. One key, one workspace. Lovable binds each key to a single workspace. To cover several workspaces, create a key in each and connect them as separate instances. IP allowlist. Lovable can restrict a key to an IP allowlist and can require one on every key. A request from any other address fails with 403. Add ConfigView’s outbound IPv4 address, and update the list if that address ever changes. No audit logs through the API. Lovable offers audit logs (Enterprise) only in its admin interface and as a scheduled export to S3, GCS, Azure Blob, Splunk or Log Analytics. There is no endpoint to read them, so ConfigView does not collect them. Point the export at your SIEM if you need the history. No last-active date. Lovable’s member list has no last sign-in, so ConfigView cannot flag inactive members. Role, SCIM provisioning and project ownership are the signals. SCIM flag. The member list does not return whether SCIM provisioned a member. ConfigView makes a second read filtered to SCIM-managed members and marks them. If that read fails the flag is left empty rather than guessed. Published host only. For a published project ConfigView stores only the host of its URL, never a path or query. Eventually consistent. Lovable says project and member lists, project counts and Security Center membership data can lag a recent change. A change made minutes ago may show up on the next run. Rate limit. Lovable applies a sliding-window limit per API key but does not publish the number. ConfigView paces itself at 60 requests a minute, waits as long as Lovable asks when it answers 429, and reads 100 rows per page. The collaborator list is read once per project, so a workspace with many projects takes proportionally longer.What isn’t collected
- Project source code, prompts, chat messages and AI-written project descriptions
- Project screenshots
- Security scan detail, per-project findings (they can contain code snippets) and personal-data labels
- Security Center explanation text
- The path or query of any published URL
- Audit logs
- API key values