SPsponsorunited
PhantomBuster monitor

Turn LinkedIn scraping off

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.

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)
  • Auth
    HTTP bearer

Request body

fingerprintstring 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

Turned off, or already off

alreadyDisabledboolean required

True when every flag was already off, so nothing was written.

notifiedboolean 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.

Example response

{
  "notified": true,
  "flags": [
    {
      "setting": "user-linkedin-scraping",
      "key": "on"
    }
  ]
}

Changes

No recorded changes to this operation across all 2 revisions of this API.