> ## 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. > Skips one step of a running campaign for a single lead. # Skip Step for Lead The lead is not stopped: the step never runs and the lead continues with the next one after that step's own delay. A step the lead already ran is unaffected — nothing already sent changes. A skip cannot be undone, here or in the lemlist app. Condition steps can never be skipped (`422`). ## OpenAPI ````yaml post /campaigns/{campaignId}/leads/{leadIdOrEmail}/steps/{stepId}/skip 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/{leadIdOrEmail}/steps/{stepId}/skip: parameters: - name: campaignId in: path required: true description: The unique identifier of the campaign example: cam_A1B2C3D4E5F6G7H8I9 schema: type: string - name: leadIdOrEmail in: path required: true description: The unique identifier or email of the lead example: lea_A1B2C3D4E5F6G7H8I9 schema: type: string - name: stepId in: path required: true description: >- The unique identifier of the step, from GET /campaigns/{campaignId}/sequences example: stp_A1B2C3D4E5F6G7H8I9 schema: type: string post: tags: - Leads summary: Skip Step for Lead description: Skip one step of a running campaign for a single lead. Cannot be undone. parameters: [] responses: '200': description: >- The step is skipped. `skipped` is `false` when it was already skipped: an idempotent no-op, not an error. content: application/json: schema: type: object properties: skipped: type: boolean example: skipped: true '400': description: >- A path identifier is malformed (JSON body carrying `ROUTE_BAD_REQUEST`), or no API key was supplied (plain text). content: application/json: example: error: Route bad request code: ROUTE_BAD_REQUEST text/plain: example: no api key provided '401': description: Unauthorized - invalid or missing API key content: text/plain: example: The authentication you supplied is incorrect '404': description: >- `STEP_SKIP_CAMPAIGN_NOT_FOUND`, `STEP_SKIP_LEAD_NOT_FOUND` or `STEP_SKIP_STEP_NOT_FOUND` - the campaign, the lead or the step does not exist in this workspace. content: application/json: example: error: Lead not found in this campaign code: STEP_SKIP_LEAD_NOT_FOUND '405': description: Method not allowed - this endpoint only accepts POST '422': description: >- `STEP_SKIP_STEP_IS_CONDITION` - a condition step can never be skipped. content: application/json: example: error: A condition step cannot be skipped code: STEP_SKIP_STEP_IS_CONDITION '429': description: Rate limit exceeded - 20 requests per 2 seconds per API key components: securitySchemes: basicAuth: type: http scheme: basic ````