> ## 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 a specific contact by their ID or email address. # Get Contact 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. ; }; The path takes a lemlist contact id (`ctc_xxx`) or an email address. To find a contact from its CRM record id, use [`GET /contacts?crmIds=`](/api-reference/endpoints/contacts/get-many-contacts). ## OpenAPI ````yaml get /contacts/{idOrEmail} 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}: parameters: - name: idOrEmail in: path required: true description: The unique identifier or email of the contact example: ctc_XXBXpAxmxwg24IzBI schema: type: string get: tags: - Contacts summary: Get Contact description: >- Retrieves a contact by its lemlist id (`ctc_xxx`) or email address. The path does not take a CRM record id: use `GET /contacts?crmIds=` for that. parameters: [] responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/Contact' example: _id: ctc_xW8Ou6C03Csv8vatp teamId: tea_8QvkOiBfPdb2ZRhHi fullName: John Doe email: support@lemlist.com fields: firstName: John jobTitle: Growth Engineer lastName: Doe industry: Technology isActiveInCampaigns: false lastCampaign: NEW TO DELETE lastLeadMarkedAsInterestedDate: '2025-10-28T02:12:31.971Z' leadStatus: Marked as not Interested by api campaigns: - campaignId: cam_bSn8EORHQxbWPjHvu campaignState: running leadState: review leadId: lea_fiDpiGV585wy3Oii2 ownerId: usr_ahfFktBBHUIxbVG5P createdAt: '2025-10-28T00:40:37.917Z' createdBy: usr_ahfFktBBHUIxbVG5P unsubscribed: false '400': description: >- `Bad team`, or a path value that is neither a contact id nor an email address. content: application/json: schema: $ref: '#/components/schemas/ApiErrorMessage' example: error: 'Match error: Failed Match.Where validation in field [0]' '401': description: The authentication you supplied is incorrect content: text/plain: example: The authentication you supplied is incorrect '404': description: No contact matches this id or email. content: application/json: schema: $ref: '#/components/schemas/ApiErrorMessage' example: error: Contact not found '405': description: Method not allowed components: schemas: Contact: type: object description: >- A contact record in your CRM, as the lookups (`GET /contacts?idsOrEmails=`, `GET /contacts?crmIds=`, `GET /contacts/{idOrEmail}`) return it. Not to be confused with a lead which is a contact specifically added to a campaign. properties: _id: type: string description: Unique contact identifier teamId: type: string description: Team identifier the contact belongs to fullName: type: string description: Contact's calculated full name email: type: string format: email description: Contact's primary email address fields: type: object description: >- Contact fields, standard (`firstName`, `lastName`, `phone`, `jobTitle`...) and custom additionalProperties: true campaigns: type: array description: List of campaigns the contact is associated with items: type: object properties: campaignId: type: string campaignState: type: string leadState: type: string leadId: type: string linkedinUrl: type: string description: Contact's LinkedIn profile URL linkedinUrlSalesNav: type: string description: Contact's LinkedIn Sales Navigator URL ownerId: type: string description: ID of the user who owns this contact createdAt: type: string format: date-time description: Contact creation timestamp createdBy: type: string description: ID of the user who created the contact unsubscribed: type: boolean description: >- Whether the contact is globally unsubscribed. When true, no outreach will be sent to this contact. phonesStatuses: type: array description: Verification status of each verified phone number. items: type: object properties: phone: type: string description: The phone number, as stored in `fields` status: type: string enum: - valid - invalid crmSync: type: object description: >- CRM sync status for the contact, resolved against the team's active CRM provider (Hubspot, Salesforce, or Pipedrive). Only present when a CRM is connected and the contact has a record in it. `crmRecordId` maps a `crmIds` lookup back to the ids sent. properties: provider: type: string enum: - hubspot - salesforce - pipedrive description: Active CRM provider for the team. crmRecordId: type: string nullable: true description: >- Identifier of the contact record on the CRM side. `null` when the lemlist contact has not been synced yet. syncDisabled: type: boolean description: When `true`, automatic sync is paused for this contact. errors: type: array description: >- List of recent sync errors. Empty when the contact is synced cleanly. items: type: object properties: type: type: string description: >- Coarse error category (e.g. `CONNECT_FAILED`, `CREATE_FAILED`, `UPDATE_FAILED`). reason: type: string description: >- Specific error reason (e.g. `UNIQUE_INDEX_ERROR_CONTACT`, `INVALID_EMAIL`, `PROPERTY_DOESNT_EXIST`). raisedAt: type: string format: date-time description: Timestamp when the error was last raised. metadata: type: object additionalProperties: true description: >- Extra context. For `UNIQUE_INDEX_ERROR_COMPANY`, contains `alreadyExistingCompanyId` — the lemlist company that already occupies the conflicting CRM record. Use it to remap contacts onto the right lemlist company before deleting the duplicate. fieldRejections: type: array description: >- Values lemlist refused to write on this contact, each with its reason. Empty when none. Filter the list endpoint to only flagged contacts via `GET /contacts?fieldRejectionReason=...`. items: $ref: '#/components/schemas/FieldRejection' ApiErrorMessage: type: object description: Error answered as a plain message by the contact and company endpoints. properties: error: type: string description: Human-readable explanation. required: - error FieldRejection: type: object description: >- A value lemlist refused to write on a Contact or Company, with the reason why. Surfaced under `fieldRejections[]` on those objects; filter a list endpoint to only flagged records via the `fieldRejectionReason` query param. properties: field: type: string description: >- The record field the rejected value targeted (e.g. `emails`, `linkedinUrl`, `domain`). reason: type: string description: >- Why the value was rejected, prefixed by its origin — `enrichment_*` (raised while enriching) or `crm_sync_*` (raised during CRM sync). Same values accepted by the `fieldRejectionReason` query param. source: type: string description: >- Where the rejection came from — an enrichment source (`lemrich`) or a CRM provider (`hubspot`, `salesforce`, `pipedrive`). conflictingRecordId: type: string description: >- The lemlist record that already holds the value, when the rejection identifies one — use it to merge or remap before resolving the duplicate. Always a lemlist id (`ctc_…` for a contact, `cpn_…` for a company), never a CRM record id. Omitted otherwise. rejectedValue: type: string description: The value that was refused. rejectedAt: type: string format: date-time description: When the rejection was recorded. securitySchemes: basicAuth: type: http scheme: basic ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.