Skip to main content
POST
/
api
/
v1
/
connected-accounts
/
claim
Claim Connected Account
curl --request POST \
  --url https://api.example.com/api/v1/connected-accounts/claim \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "claim_token": "<string>"
}
'
{
  "previous_owner_user_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "linkedin_slug": "<string>",
  "success": true,
  "next_action": "reconnect"
}

Documentation Index

Fetch the complete documentation index at: https://docs.bavlio.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Request body for POST /api/v1/connected-accounts/claim.

claim_token
string
required
Required string length: 10 - 4096

Response

Successful Response

Response from a successful ownership transfer.

The claim flow only DISCONNECTS the previous owner's row to free the canonical slug; the requesting user re-runs /connect to register their own Unipile session, which then succeeds because the slug is no longer held.

previous_owner_user_id
string<uuid>
required

User ID of the previous owner (for client-side audit logging only).

linkedin_slug
string
required

The canonical slug that was freed. The frontend uses this to prompt the user to re-run /connect and complete onboarding.

success
boolean
default:true
next_action
string
default:reconnect

Always 'reconnect'. The frontend should redirect the user back to the connect flow so they can register their own Unipile session.