List personal data findings
This endpoint lets you retrieve a list of all personal information detected in your project, sorted from newest to oldest. It includes items that are open, ignored, or already resolved.
Security teams and enterprise workspace administrators who need to audit sensitive user data found in a project.
Do this, in order
- 1
Confirm that your workspace is on an Enterprise plan and that personal data detection is turned on.
This endpoint requires an Enterprise plan and returns a 404 error if personal data detection is disabled.
- 2
Generate an API key with the projects:read scope in your workspace settings.
Requests without an authorized API key or with insufficient scopes will be rejected with an error.
- 3
Send a GET request to /v1/projects/{project_id}/pii-labels with your API key in the headers.
This retrieves the newest personal data detections for the specified project.
- 4
Read pagination.next_cursor and pass it as the cursor query parameter in subsequent calls if pagination.has_more is true.
Results are capped at a maximum of 100 items per request, so cursors are necessary to retrieve full records.
Paste this into your project
Create a data privacy review page that calls the Lovable GET /v1/projects/{project_id}/pii-labels API endpoint. Show a clean list of detected personal data findings with their status, detection timestamp, and pagination buttons using the response cursor to browse through pages.Words decoded
- PII
- Personally Identifiable Information, which refers to any data that can identify an individual person, such as names, phone numbers, or email addresses.
- Cursor
- A unique marker used to fetch the next set of results without losing your place in the list.
- Scope
- The specific permission assigned to an API key defining what actions it is allowed to take.
Where people get stuck
- Leaving personal data detection turned off in the workspace will produce a 404 error instead of an empty list.
- Attempting to call this endpoint without an Enterprise plan will result in a payment required error.
- Using an API key missing the projects:read or projects:write scope causes a 403 insufficient scope failure.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.