---
title: "Bulk Trigger Historical Pull"
method: POST
path: "/v2/link/bulk_trigger_historical_pull"
tags: ["link"]
---

# Bulk Trigger Historical Pull

`POST /v2/link/bulk_trigger_historical_pull`

## Request body

- BulkTriggerHistoricalPullBody
  - `user_ids` string[], required
  - `provider` 'oura' | 'fitbit' | 'garmin' | 'strava' | 'wahoo' | 'ihealth' | 'withings' | 'google_fit' | 'dexcom_v3' | 'polar' | 'cronometer' | 'omron' | 'whoop_v2' | 'my_fitness_pal_v2' | 'ultrahuman' | 'runkeeper' | 'google_health', required — ℹ️ This enum is non-exhaustive.
  - `wait_for_completion` boolean — Whether or not the endpoint should wait for the Bulk Op to complete before responding. When `wait_for_completion` is enabled, the endpoint may respond 200 OK if the Bulk Op takes less than 20 seconds to complete. Otherwise, the endpoint always responds with 202 Created once the submitted data have been enqueued successfully. You can use the [List Bulk Ops](https://docs.tryvital.io/api-reference/link/list-bulk-ops) endpoint to inspect the progress of the Bulk Op.

## Response `200`

Successful Response

- unknown

## Other responses

- `202` — Accepted
- `422` — Validation Error

---

[API](https://skmtc.net/tryvital/apis/junction-api.md) · [All operations](https://skmtc.net/tryvital/apis/junction-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tryvital/junction-api/revisions/1a22b97afb3a/schema)