> ## 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 saved searches of your team. # List Saved Searches 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. ; }; Saved searches are team-shared: every member sees the same list. Results are sorted by name. Use `mode` to restrict the list to one search mode — saved searches created before modes existed are returned for both. ## OpenAPI ````yaml get /database/saved-searches 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: [] tags: - name: Enrichment Providers description: >- The data providers lemlist can call to find an email or a phone. Internal providers are paid with lemlist credits and always available. External providers run on your own account: connect one by saving its API key, and it becomes available to your waterfalls. `GET /enrichments/providers` is the catalog of provider ids accepted by the waterfall endpoints. - name: Enrichment Waterfalls description: >- Control which data providers lemlist calls when enriching a contact, and in which order. A waterfall is an ordered list of providers for one enrichment `type` (`email` or `phone`). Providers are tried one after the other until one returns a result. Every team has exactly one default waterfall per type (`isDefault: true`). While its `editor` is `lemlist` it follows the lemlist behaviour: providers you connected with your own API key are tried first, then internal providers in a random order. Once a team member edits its provider list, `editor` becomes that user's id and the list is followed as is; resetting it hands it back to `lemlist`. Custom waterfalls (`isDefault: false`) carry `conditions` on the contact being enriched, keyed by contact property; every key present must match. When a contact is enriched, lemlist runs a single waterfall: the custom waterfall of the requested type whose conditions match the contact, or the default waterfall when none does. If several match, the one with the most condition keys wins, then the most recently updated. Only that waterfall runs; when it finds nothing, the enrichment ends without falling back to another one. paths: /database/saved-searches: get: tags: - People Database summary: List Saved Searches description: >- Lists the People Database saved searches of your team, sorted by name. Saved searches are team-shared: every member sees the same list. operationId: listSavedSearches parameters: - name: mode in: query required: false description: >- Restrict the list to saved searches of one search mode. Saved searches created before modes existed are returned for both modes. Omit to return every saved search of the team. schema: type: string enum: - leads - companies example: leads responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/SavedSearchListResponse' example: data: - _id: lss_ExAmPlE4f7Kq2Wz9x name: Paris SaaS founders mode: leads filters: - filterId: currentTitle in: - Founder out: [] - filterId: country in: - France out: [] createdAt: '2026-09-14T08:30:00.000Z' lastResultsCount: 1240 lastResultsCountUpdatedAt: '2026-09-14T08:30:00.000Z' '400': description: Validation error - invalid query parameters content: application/json: schema: $ref: '#/components/schemas/PersonaError' example: error: Parameter mode is invalid code: API_INVALID_MODE '401': description: >- Unauthorized - invalid or missing API key. An API key with no user attached answers `{ "error": "Route unauthorized", "code": "ROUTE_UNAUTHORIZED" }` in JSON instead. content: text/plain: example: The authentication you supplied is incorrect '405': description: Method not allowed content: application/json: schema: $ref: '#/components/schemas/PersonaError' example: error: Route bad method code: ROUTE_BAD_METHOD components: schemas: SavedSearchListResponse: type: object properties: data: type: array description: The team's saved searches, sorted by name items: $ref: '#/components/schemas/SavedSearch' PersonaError: type: object description: >- Error envelope returned by the persona, saved-search and Get Database Filters endpoints. properties: error: type: string description: Human-readable explanation of the failure code: type: string description: Machine-readable error code, stable across releases SavedSearch: type: object description: >- A People Database saved search: a named set of People Database filters saved by your team. It appears in the "Saved searches" menu of the People Database. properties: _id: type: string description: Unique saved search identifier example: lss_ExAmPlE4f7Kq2Wz9x name: type: string description: Display name. Unique within your team. example: Paris SaaS founders mode: type: string enum: - leads - companies description: >- Search mode the filters target. Always set: saved searches created before modes existed read as `leads`. example: leads filters: type: array description: >- People Database filters of the saved search. Same shape as the search endpoints accept, so they can be sent back as is to [Search People Database](/api-reference/endpoints/people-database/search-people-database) or [Search Companies Database](/api-reference/endpoints/people-database/search-companies-database). items: $ref: '#/components/schemas/PersonaFilter' createdAt: type: string format: date-time description: Date the saved search was created example: '2026-09-14T08:30:00.000Z' lastResultsCount: type: number description: >- Number of results the saved search returned the last time it was saved or run example: 1240 lastResultsCountUpdatedAt: type: string format: date-time description: Date `lastResultsCount` was last computed example: '2026-09-14T08:30:00.000Z' PersonaFilter: type: object description: >- One People Database filter, as stored in a persona or a saved search. `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 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.