> ## 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. > Creates a new lead and adds it to a specific campaign. # Create Lead in Campaign 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 post /campaigns/{campaignId}/leads/ 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: /campaigns/{campaignId}/leads/: parameters: - name: campaignId in: path required: true description: The unique identifier of the campaign example: cam_A1B2C3D4E5F6G7H8I9 schema: type: string post: tags: - Leads summary: Create Lead in Campaign parameters: - name: deduplicate in: query required: false description: >- Search email address in other campaigns. Will not insert the lead if email address already exists. Default: false example: 'true' schema: type: boolean - name: linkedinEnrichment in: query required: false description: 'Run the LinkedIn enrichment. Default: false' example: 'true' schema: type: boolean - name: findEmail in: query required: false description: 'Find verified email. Default: false' example: 'true' schema: type: boolean - name: verifyEmail in: query required: false description: 'Verify existing email (debounce). Default: false' example: 'true' schema: type: boolean - name: findPhone in: query required: false description: 'Find phone number. Default: false' example: 'true' schema: type: boolean requestBody: content: application/json: schema: type: object properties: email: type: string description: Email of the lead firstName: type: string description: First name of the lead lastName: type: string description: Last name of the lead companyName: type: string description: Company name jobTitle: type: string description: Job title linkedinUrl: type: string description: LinkedIn profile URL picture: type: string description: Profile picture URL phone: type: string description: Phone number companyDomain: type: string description: Company domain icebreaker: type: string description: Personalized icebreaker message timezone: type: string description: >- Lead's timezone in IANA format (e.g., Europe/Paris, America/New_York) contactOwner: type: string description: Contact owner (user ID or user login email) example: email: support@lemlist.com firstName: John lastName: Doe companyName: lemlist jobTitle: Developer linkedinUrl: https://www.linkedin.com/in/johndoe phone: +33 123456789 timezone: Europe/Paris contactOwner: login_email@lemlist.com responses: '200': description: Success content: application/json: schema: type: object properties: campaignId: type: string campaignName: type: string email: type: string format: email firstName: type: string lastName: type: string companyName: type: string jobTitle: type: string companyDomain: type: string _id: type: string isPaused: type: boolean description: Whether the lead is paused in the campaign contactId: type: string description: Associated contact ID example: campaignId: cam_bSn8EORHQxbWPjHvu campaignName: NEW TO DELETE firstName: John lastName: Doe companyName: lemlist jobTitle: GTM Engineer companyDomain: example.com email: support@lemlist.com _id: lea_fiDpiGV585wy3Oii2 isPaused: false contactId: ctc_xW8Ou6C03Csv8vatp '400': description: 'Possible errors: No API key provided / Bad team' 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 '403': description: User linked to this API key is blocked content: text/plain: example: User linked to this API key is blocked '404': description: 'Possible errors: No user found for this API key / Campaign not found' content: text/plain: example: No user found for this API key components: securitySchemes: basicAuth: type: http scheme: basic ````