> ## Documentation Index
> Fetch the complete documentation index at: https://developer.lemlist.com/llms.txt
> Use this file to discover all available pages before exploring further.
> Retrieves the People Database personas saved by your team.
# List Personas
export const SnippetObjectReference = ({objectName, objectPath = null}) => {
const lowerCaseObjectName = objectName.toLowerCase();
if (lowerCaseObjectName === 'lead' || lowerCaseObjectName === 'leads') {
return
This endpoint uses the {objectName} object. Make sure to also check the {lowerCaseObjectName === 'lead' ? 'Contact' : 'Lead'} object to understand the distinction between the two.
;
}
return
This endpoint uses the {objectName} object.
;
};
Personas are team-shared: every member sees the same list. Results are sorted by creation date, most recent first, and capped at 200. Use `mode` to restrict the list to one search mode.
The persona lemlist auto-generates from your AI business context is never returned — only the personas your team created are.
This endpoint is in closed beta. It answers `403` with the code `BETA_NOT_ENABLED` unless the personas beta is enabled for your team.
## OpenAPI
````yaml get /database/personas
openapi: 3.0.0
info:
title: lemlist API
version: 1.0.0
description: >-
Welcome to the lemlist Developer Documentation.
lemlist is very customizable and open. You'll find on this page all the API
and integration you can do with lemlist.
# Rate Limit
lemlist's API rate limits requests in order to prevent abuse and overload of
our services.
Rate limits are applied on all routes and per API key performing the
request.
The rate limits are **20** requests per **2** seconds.
The response provides any information you may need about it:
| Header | Description |
| --- | --- |
| Retry-After | The number of seconds in which you can retry |
| X-RateLimit-Limit | The maximum requests in that time |
| X-RateLimit-Remaining | The number of remaining requests you can make |
| X-RateLimit-Reset | The date when the rate limit will reset |
_Example of values for the rate limit headers_
``` json
{
"Retry-After": 2,
"X-RateLimit-Limit": 20,
"X-RateLimit-Remaining": 7,
"X-RateLimit-Reset" : "Tue Feb 16 2021 09:02:42 GMT+0100 (Central European Standard Time)"
}
```
# Definitions
## Team
A team is the entity of lemlist that can handle users and billing.
## Credits
Credits are the coins a team uses to enrich emails, LinkedIn URLs, etc. via
the enrich route. Each enrichment feature needs a certain amount of credits
to run.
## User
You use a user account to connect to lemlist and send messages via the
connected emails or LinkedIn account.
## Campaign
A campaign is the entity to automate outreach. A campaign has multiple
sequences composed of steps.
## Lead
A lead is a person that you try to contact via a campaign.
## Activity
An activity is the history of all the steps.
## Unsubscribe
An unsubscribe occurs when a person decides they don't want to receive
emails from you anymore.
# Authentication
All API routes use the dedicated subdomain `api.lemlist.com`.
lemlist uses API keys to allow access to the API. You can get your lemlist
API key at our [integration
page](https://app.lemlist.com/settings/integrations).
You need to add the `Authorization` header using the `Basic` authentication
type. `login:password` **where the login is always empty and the password is
the API key**.
⚠️ **Don't forget to add the semicolon (**`:`**) before your API key in curl
command.**
> To authorize, use this code:
``` shell
curl https://api.lemlist.com/api/team \
--user ":YourApiKey"
```
**Make sure to replace** **`YourApiKey`** **with your API key.**
# Give feedback
If you want to report a bug, ask for data, or share with us a use case,
please fill this [form](https://lemlist.typeform.com/to/mfVlkyGf). It will
help us centralize your needs!
servers:
- url: https://api.lemlist.com/api
security:
- basicAuth: []
paths:
/database/personas:
get:
tags:
- People Database
summary: List Personas
description: >-
Lists the personas saved by your team. A persona is a named, reusable
set of People Database filters; its id can then be referenced elsewhere
in the API, for example through the `persona` filter of a Signal Agent.
Personas are team-shared: every member sees the same list. Results are
sorted by creation date, most recent first, and capped at 200. The
auto-generated persona lemlist derives from your AI business context is
never returned; only the personas your team created are.
This endpoint is in closed beta and answers `403` unless the beta is
enabled for your team.
operationId: listPersonas
parameters:
- name: mode
in: query
required: false
description: >-
Restrict the list to personas of one search mode. Omit to return
every persona of the team.
schema:
type: string
enum:
- leads
- companies
example: leads
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/PersonaListResponse'
example:
data:
- _id: pdp_ExAmPlE1234567890a
name: SaaS founders
mode: leads
filters:
- filterId: currentTitle
in:
- Founder
out: []
- filterId: country
in:
- France
out: []
createdAt: '2026-07-31T09:12:00.000Z'
updatedAt: '2026-07-31T09:12:00.000Z'
'400':
description: Validation error - invalid query parameters
content:
application/json:
schema:
$ref: '#/components/schemas/PersonaError'
example:
error: >-
Parameter "mode" must be "leads" or "companies"; user personas
currently accept "leads" only
code: PEOPLE_DATABASE_PERSONA_API_INVALID_MODE
'401':
description: Unauthorized - invalid or missing API key
content:
application/json:
schema:
$ref: '#/components/schemas/PersonaError'
example:
error: Route unauthorized
code: ROUTE_UNAUTHORIZED
'403':
description: The personas beta is not enabled for your team
content:
application/json:
schema:
$ref: '#/components/schemas/PersonaError'
example:
error: Beta is not enabled
code: BETA_NOT_ENABLED
'500':
description: Internal server error
content:
application/json:
schema:
$ref: '#/components/schemas/PersonaError'
example:
error: Internal error
code: INTERNAL_ERROR
components:
schemas:
PersonaListResponse:
type: object
properties:
data:
type: array
description: The team's personas, most recently created first
items:
$ref: '#/components/schemas/Persona'
PersonaError:
type: object
description: Error envelope returned by the persona endpoints.
properties:
error:
type: string
description: Human-readable explanation of the failure
code:
type: string
description: Machine-readable error code, stable across releases
Persona:
type: object
description: >-
A People Database persona: a named, reusable set of People Database
filters saved by your team. A persona id can be referenced elsewhere in
the API, for example through the `persona` filter of a Signal Agent.
properties:
_id:
type: string
description: Unique persona identifier
example: pdp_ExAmPlE1234567890a
name:
type: string
description: Display name. Unique within your team.
example: SaaS founders
mode:
type: string
description: Search mode the filters target
enum:
- leads
- companies
example: leads
filters:
type: array
description: People Database filters defining the persona
items:
$ref: '#/components/schemas/PersonaFilter'
createdAt:
type: string
format: date-time
description: Date the persona was created
example: '2026-07-31T09:12:00.000Z'
updatedAt:
type: string
format: date-time
description: Date of the last modification
example: '2026-07-31T09:12:00.000Z'
PersonaFilter:
type: object
description: >-
One People Database filter of a persona. `in` includes matching values,
`out` excludes them. There is no `type` property: it is derived from
`filterId` server-side.
required:
- filterId
properties:
filterId:
type: string
description: >-
People Database filter identifier. Use [Get Database
Filters](/api-reference/endpoints/people-database/get-database-filters)
to discover the valid ids.
example: currentTitle
in:
type: array
description: Values to include
items:
type: string
example:
- Founder
out:
type: array
description: Values to exclude
items:
type: string
example: []
exactMatch:
type: boolean
description: Exact-match toggle, for the text filters that support it
securitySchemes:
basicAuth:
type: http
scheme: basic
````