---
title: "Get a recurring export"
method: GET
path: "/v1/extractions/recurring/{schedule_id}/"
tags: ["LinkedIn Extraction"]
---

# Get a recurring export

`GET /v1/extractions/recurring/{schedule_id}/`

## Request

- Base URL: `https://api.evaboot.com`
- URL: `https://api.evaboot.com/v1/extractions/recurring/{schedule_id}/`
- Auth: HTTP bearer

One recurring export. Unknown, stopped, and another account's ids are not found.

## Path parameters

- `schedule_id` string, uuid, required

## Response `200`

OK

- RecurringExportOut: One recurring export the caller can still manage.
  - `id` string, uuid, required: Schedule id. Pass it to get, update, and delete.
  - `name` string, required: Name copied onto each future run.
  - `frequency` string, required: `daily`, `weekly`, or `monthly`.
  - `paused` boolean, required: When `true`, the scheduler skips this schedule.
  - `search_url` string, required: The saved search on LinkedIn, without the new-since-last-run filter.
  - `lead_search` boolean, required: `true` for a people search, `false` for a company search.
  - `template_extraction_id` string, nullable: The extraction this schedule was started from, when it still exists. Same id `GET /v1/extractions/{extraction_id}/` accepts.
  - `last_execution_at` string, date-time, nullable: When the schedule last launched a run. Null before the first automatic run.
  - `next_execution_at` string, date-time, nullable: When the next run is due. A paused schedule still reports the date it would have used.
  - `runs` integer: Exports this schedule has already produced.
  - `leads` integer: Leads collected across those runs.
  - `destinations` RecurringDestinationOut[]: Automatic integrations that receive each run: those sending all exports, all recurring exports, this recurring export, or the folder its runs are filed in. People-only integrations are left out of a company search.
    - `id` string, uuid, required: Integration id.
    - `type` string, required: Integration type.
    - `label` string, required: Integration name.

## Other responses

- `401`: The API key is missing, malformed or unknown.
- `404`: No such resource, or it belongs to another account.
- `422`: The request body or a supplied URL failed validation.

---

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