LinkedIn Extraction

Create a recurring export

Schedule an extraction you already launched, or a Sales Navigator people or company search URL, so Evaboot repeats it daily, weekly, or monthly. Pass exactly one of extraction_id or url.

This does not scrape. The next run is one interval after this call and contains only leads new since now, including when the original extraction is still in progress. Each run uses your connected Sales Navigator account, spends credits, and counts against the daily quota. With no credits or no connected account, that run is skipped and the next date still moves forward.

A URL that already contains savedSearchId is scheduled as that saved search. Nothing is saved again. Any other people or company search, including a people search filtered on an account list, is saved once on your Sales Navigator seat and then scheduled as that search. A search you already automate is not duplicated: the existing schedule's cadence is updated and created is false.

Lists and single profiles are rejected, and so is a search filtered on the temporary company lists of an account-based search agent job: schedule its accounts_url instead.

post/v1/extractions/recurring/

Request

  • Base URL: https://api.evaboot.com
  • URL: https://api.evaboot.com/v1/extractions/recurring/
  • Auth: HTTP bearer

Request body

extraction_idstring nullable

Identifier of an existing extraction, as returned by POST /v1/extractions/url/ and by the list endpoint's search_id. People and company searches only. Lists and single profiles cannot recur. Pass this or url, not both.

urlstring nullable

A Sales Navigator people or company search URL. When it already contains savedSearchId, that saved search is scheduled and nothing is saved again. Any other people or company search is saved once on your Sales Navigator seat, then scheduled. A people search filtered on an account list stays that lead search. Pass this or extraction_id, not both.

frequency'daily' | 'weekly' | 'monthly' required

How often a new export of leads found since the previous run is launched.

Example request

{
  "extraction_id": "ext-12345",
  "url": "https://www.linkedin.com/sales/search/people?savedSearchId=2012510114",
  "frequency": "weekly"
}

Response

OK

idstring uuid required

Schedule id. Pass it to get, update, and delete.

namestring required

Name copied onto each future run.

frequencystring required

daily, weekly, or monthly.

pausedboolean required

When true, the scheduler skips this schedule.

search_urlstring required

The saved search on LinkedIn, without the new-since-last-run filter.

lead_searchboolean required

true for a people search, false for a company search.

template_extraction_idstring nullable

The extraction this schedule was started from, when it still exists. Same id GET /v1/extractions/{extraction_id}/ accepts.

last_execution_atstring date-time nullable

When the schedule last launched a run. Null before the first automatic run.

next_execution_atstring date-time nullable

When the next run is due. A paused schedule still reports the date it would have used.

runsinteger

Exports this schedule has already produced.

leadsinteger

Leads collected across those runs.

createdboolean required

true when a new schedule was stored. false when this search was already recurring and only the cadence changed.

Example response

{
  "name": "Weekly CTOs",
  "frequency": "weekly",
  "lead_search": true,
  "runs": 3,
  "leads": 120,
  "destinations": [
    {
      "type": "hubspot",
      "label": "Sales CRM"
    }
  ],
  "created": true
}

Changes

No recorded changes to this operation across all 1 revision of this API.