> ## 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 notes attached to a specific contact, resolved by its ID or email address. # Get Contact Notes 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. ; }; ## OpenAPI ````yaml get /contacts/{idOrEmail}/notes 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: /contacts/{idOrEmail}/notes: parameters: - name: idOrEmail in: path required: true description: The unique identifier (`ctc_xxx`) or email of the contact example: ctc_XXBXpAxmxwg24IzBI schema: type: string get: tags: - Contacts summary: Get Contact Notes description: >- Retrieves the notes attached to a contact, newest first by default. The contact is resolved by its id (`ctc_xxx`) or email within your team. Only notes are returned, not the contact's other activities. Use `page` and `limit` to paginate: the response carries the page in `data` and the number of notes in `total`; a contact without notes answers `200` with an empty `data`. parameters: - name: limit in: query required: false description: >- Number of notes per page. Default: 100. Maximum: 100. A missing, invalid or non-positive value falls back to 100. example: '2' schema: type: integer - name: page in: query required: false description: >- Page number to retrieve, starting at 1. Default: 1. An invalid value falls back to 1; a page beyond the last one answers an empty `data`. example: '1' schema: type: integer - name: sortBy in: query required: false description: >- The field to sort by. Only `createdAt` is supported; any other value is ignored. example: createdAt schema: type: string enum: - createdAt - name: sortOrder in: query required: false description: >- The sort direction. Default: `desc` (newest first). Any other value sorts ascending. example: desc schema: type: string enum: - asc - desc responses: '200': description: Success content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/ContactNote' total: type: integer description: Number of notes attached to the contact, across all pages required: - data - total example: data: - _id: act_j0NrG6rYEPP9TMmWC teamId: tea_8QvkOiBfPdb2ZRhHi contactId: ctc_XXBXpAxmxwg24IzBI createdAt: '2026-09-28T09:12:00.653Z' note: Asked for a demo next week userId: usr_ahfFktBBHUIxbVG5P - _id: act_BYF2j06u0wgeLncub teamId: tea_8QvkOiBfPdb2ZRhHi contactId: ctc_XXBXpAxmxwg24IzBI createdAt: '2026-09-21T15:40:10.605Z' note: Met at SaaStock userId: usr_ahfFktBBHUIxbVG5P total: 2 '400': description: >- A request without an API key answers `400` with the plain-text message `no api key provided`. Query parameters never answer `400`: a value outside the contract falls back to its default, as on `GET /companies/{companyId}/notes`. content: text/plain: example: no api key provided '401': description: The authentication you supplied is incorrect content: text/plain: example: The authentication you supplied is incorrect '404': description: >- No contact with this id or email in your team (a path that is not valid percent-encoding matches no contact) content: application/json: schema: type: object properties: error: type: string example: error: Contact not found '405': description: Method not allowed components: schemas: ContactNote: type: object description: >- A text note attached to a contact record, as returned by `GET` and `POST /contacts/{idOrEmail}/notes`. properties: _id: type: string description: Unique note identifier (`act_xxx`) teamId: type: string description: Team ID that owns the contact contactId: type: string description: Parent contact ID (`ctc_xxx`) note: type: string description: Note text content userId: type: string description: ID of the user who wrote the note createdAt: type: string format: date-time description: Creation timestamp securitySchemes: basicAuth: type: http scheme: basic ````