TRtryvital
link

Bulk Trigger Historical Pull

Changed on
post/v2/link/bulk_trigger_historical_pull

Request

  • Base URL
    https://api.us.junction.com
  • URL
    https://api.us.junction.com/v2/link/bulk_trigger_historical_pull
  • Auth
    API key in header x-vital-api-key

Request body

user_idsstring[] 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_completionboolean

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 endpoint to inspect the progress of the Bulk Op.

Response

Successful Response

unknown required

Changes