Connect a new channel account (LinkedIn, WhatsApp, etc.) to your API key. Once connected, you receive an account_id to use in all subsequent requests.
This endpoint costs 1 credit per request.
Body Parameters
The channel platform to connect. Available: linkedin, whatsapp (more coming soon)
Account email address (required for credential-based login)
Account password (required for credential-based login)
Authentication token/cookie for direct token-based connection. Alternative to email+password.
Country code for proxy selection. Available: US, UK, FR, DE, NL, IT, IL, CA, BR, ES, IN
Optional display name for the account. Defaults to the email address.
challenge_type
string
default: "code_challenge"
Type of 2FA challenge to use if the account has two-factor authentication enabled.
code_challenge — receive a verification code via email, SMS, or authenticator app. You must then submit the code via /v2/checkpoint.
app_challenge — confirm the login directly from the LinkedIn mobile app. No code needed — just call /v2/checkpoint with the account_id after approving on the app.
Response
Whether the request was successful
The unique identifier for the connected account. Use this in all future requests.
The platform that was connected
Account status: connected (ready to use) or checkpoint_required (needs 2FA verification)
Additional information (present when checkpoint is required)
Connected Successfully
Checkpoint Required (2FA)
Error Response
{
"success" : true ,
"data" : {
"account_id" : "69c127c37cae0494dd827286" ,
"platform" : "linkedin" ,
"status" : "connected"
},
"metadata" : {
"action" : "login" ,
"credits_consumed" : 1 ,
"timestamp" : "2025-01-15T10:30:00.000000"
}
}
Login Methods
There are two ways to connect an account:
Credential-based login — provide email + password. If 2FA is enabled, you’ll receive a checkpoint_required status and need to call /v2/checkpoint.
Token-based login — provide a login_token directly. The token is encrypted and stored securely. No 2FA step needed.
Notes
The account_id returned is permanent — store it and reuse it for all API calls
Tokens are encrypted at rest using AES-256
If you receive checkpoint_required, use the /v2/checkpoint endpoint to complete verification
The country parameter determines which proxy is used for the connection
Each platform may require different parameters (e.g. WhatsApp uses phone_number)