Start a LinkedIn connect for a new sender profile
Start a LinkedIn login at TEAM level: gtm mints a cloud browser and returns its one-time login link, and the sender profile is born later, from the linkedin-accounts.created delivery. Use start_sender_profile_linkedin_connect instead when the account must land on a sender profile that already exists.
One browser source per call (two is a 422): proxy_country_code (the managed pool; offer only what list_sender_profile_linkedin_proxy_countries reports, a dry country is 422 proxy_pool_empty), custom_proxy_config (the team's own proxy) or vendor_profile_id (the team's own GoLogin profile, its proxy stays on it). public_link makes the link a two-day one for whoever holds the password, mailed to public_link_email when given (result.sent_to_email). history_since and history_scope bound what of the account's past is imported. Each call is a connect of its own: when gtm-api did not confirm the browser create or the link, the call answers 409 linkedin_connect_unconfirmed, not recoverable, since a repeat here makes another browser; prefer start_sender_profile_linkedin_connect, whose repeat picks up a browser made meanwhile. Other refusals read as on that tool (402 linkedin_sender_profiles_full, 402 subscription_required, 403 gtm_scope_missing). 501 while the gtm bridge is unconfigured.
Contract:
- MCP tool start_new_sender_profile_linkedin_connect, registry package mcp.unibox/sender_profiles, mount unibox.sender-profiles.
- Operation action, response envelope action.
- Flags: none.
Request
- Base URLhttps://beta.getsales.io/unibox/v1
- AuthHTTP bearer and API key in header Team-SID
Request body
Response
action success envelope.
Changes
No recorded changes to this operation across all 1 revision of this API.