GEgetsales
sender_profiles

Check a LinkedIn proxy

Check the team's own proxy before a LinkedIn connect routes a browser through it (custom_proxy_config on start_sender_profile_linkedin_connect): gtm-api probes it and reports whether it answers and where it exits; nothing is written. A proxy that does not answer is result.ok false with error_kind (timeout, tls, network, http_error), not an error; on success result.country_code is the country the browser will carry. The connect probes again and refuses one that stopped answering.

Contract:

  • MCP tool check_sender_profile_linkedin_proxy, registry package mcp.unibox/sender_profiles, mount unibox.sender-profiles.
  • Operation action, response envelope action.
  • Flags: read only.
post/api/sender-profiles/linkedin/check-proxy

Request

  • Base URL
    https://beta.getsales.io/unibox/v1
  • Auth
    HTTP bearer and API key in header Team-SID

Request body

ipstring required

Proxy host or IP.

portinteger required

Proxy port.

mode'http' | 'socks4' | 'socks5'

Proxy protocol; default http. There is no https mode: GoLogin cannot apply one.

usernamestring nullable

Proxy username; null = the proxy takes no credentials. Passed straight to gtm-api, never stored here.

passwordstring nullable

Proxy password. Passed straight to gtm-api and never stored here.

sender_profile_sidstring nullable

When editing an existing sender profile's own proxy, name the sender profile: a password left out is then probed as the one its browser stores (same host and username only).

Response

action success envelope.

successtrue required
operation'action' required
actionstring required

kebab-case verb; matches the route segment.

itemobject nullable required

Changes

No recorded changes to this operation across all 1 revision of this API.