---
title: "Turn LinkedIn scraping off"
method: POST
path: "/api/phantombuster-monitor/scraping/disable"
tags: ["PhantomBuster monitor"]
---

# Turn LinkedIn scraping off

`POST /api/phantombuster-monitor/scraping/disable`

## Request

- Base URL: `https://api.sponsorunited.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.sponsorunited.com/api/phantombuster-monitor/scraping/disable`
- Auth: HTTP bearer

Sets the on key of user-linkedin-scraping, contacts-linkedin-scraping and contacts-employees-linkedin-scraping to false, keeping every other key of those settings, then posts a Slack notice to the monitor channel listing the findings that led to it. The findings are only reported: the same flags are turned off whatever they say. The notice is posted after the flags are saved: when Slack does not accept it, the flags stay off, the answer says notified=false and the failure is logged as an error. The caller cannot choose the settings, and nothing here turns scraping back on; that is done by a person. Calling it when everything is already off changes nothing, posts nothing and answers alreadyDisabled=true. Requires the disable-scraping permission; limited to 10 calls an hour per caller.

## Request body

- DisableLinkedinScrapingRequest
  - `findings` PhantomBusterMonitorAlertFinding[], required: What led to this, listed in the Slack notice and the log. Nothing is decided from them: the same flags are turned off whatever they say.
    - `kind` string, required: What changed, e.g. field_removed or type_changed.
    - `path` string, required: Where in the container it changed, e.g. resultObject[].profileUrl.
    - `detail` string, nullable: One line on the change.
  - `fingerprint` string, nullable: The fingerprint of the drift alert that led to this. Only shown in the Slack notice and the log, so a person can match the two; nothing is decided from it.

## Response `200`

Turned off, or already off

- object
  - `alreadyDisabled` boolean, required: True when every flag was already off, so nothing was written.
  - `notified` boolean, required: True when Slack accepted the notice. False when nothing was turned off, or when Slack did not accept the notice after the flags were turned off.
  - `flags` object[], required
    - `setting` string, required
    - `key` string, required
    - `alreadyDisabled` boolean, required

## Other responses

- `401`: No valid token
- `403`: Caller lacks the disable-scraping permission
- `409`: One of the settings does not hold a list of keys; nothing was turned off
- `422`: Invalid request, including no findings, more than 20, or an invalid fingerprint
- `429`: More than 10 calls in the last hour
- `503`: No Slack webhook is configured; nothing was turned off

---

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