---
title: "Delete a LinkedIn scraper"
method: DELETE
path: "/linkedin-scrappers/{id}"
tags: ["LinkedIn scraper"]
---

# Delete a LinkedIn scraper

`DELETE /linkedin-scrappers/{id}`

## Request

- Base URL: `https://api.emelia.io`
- URL: `https://api.emelia.io/linkedin-scrappers/{id}`
- Auth: API key in header `Authorization`

Deletes a scraper. It disappears from the API and from the app. A Sales Navigator extraction in progress is stopped and the next chunks of a segmented extraction do not start.

Pitfalls: the deletion is logical (Emelia keeps the extracted file). A classic LinkedIn search that is already extracting is not stopped: it runs to its end (and still sends its FINISHED webhook). The Emelia list created from the scraper (`convertedListId`) is not deleted.

## Path parameters

- `id` string, required

## Response `200`

Deleted.

- ScrapperSuccessResponse
  - `success` boolean, required

## Other responses

- `400`: Unknown scraper or malformed id.
- `401`: Missing or invalid API key (`Authorization` header).
- `500`: Unexpected server error. Current behavior: also returned when the per-minute API quota of the workspace is exceeded (30 requests per minute without subscription, 100 on Start, 300 on Grow, 1,000 on Scale). A 429 would be expected; retry after a minute.

---

[API](https://skmtc.dev/emelia/apis/emelia-api.md) · [All operations](https://skmtc.dev/emelia/apis/emelia-api/llms.txt) · [OpenAPI document](https://skmtc.dev/emelia/apis/emelia-api/revisions/8c0cb435f2c4?raw)