Skip to main content
POST
/
v2
/
link
/
bulk_export
Bulk Export Connections
curl --request POST \
  --url https://api.us.junction.com/v2/link/bulk_export \
  --header 'Content-Type: application/json' \
  --header 'x-vital-api-key: <api-key>' \
  --data '
{
  "user_ids": [
    "3c90c3cc-0d44-4b50-8888-8dd25736052a"
  ],
  "next_token": "<string>"
}
'
{
  "data": [
    {
      "user_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
      "access_token": "<string>",
      "refresh_token": "<string>",
      "provider_id": "<string>",
      "expires_at": 123,
      "oauth_scopes": [
        "<string>"
      ]
    }
  ],
  "next_token": "<string>"
}
If you are planning to migrate connections, please chat with us through support channels. Link Migration endpoints are disabled by default.
You should pause the connections before bulk exporting them. Pausing stops Junction systems from refreshing the connections, ensuring the exported data is the most up-to-date.

Authorizations

​
x-vital-api-key
string
header
required

Vital Team API Key

Body

application/json
​
provider
enum<string>
required

ℹ️ This enum is non-exhaustive.

Available options:
oura,
fitbit,
garmin,
strava,
wahoo,
ihealth,
withings,
google_fit,
dexcom_v3,
polar,
cronometer,
omron,
whoop_v2,
my_fitness_pal_v2,
ultrahuman,
runkeeper,
google_health
​
user_ids
string<uuid>[] | null
​
next_token
string | null

Response

Successful Response

​
data
ConnectionRecipe · object[]
required
​
next_token
string | null
required