What it is: LeadConnector’s authenticated services API. The plugin’s primary read/write surface for account and configuration data, OAuth token exchange / refresh, optional CDN cache purge, chat-widget service endpoints, and one allowlisted host for optional funnel tracking-code downloads supplied by LeadConnector during import. What is sent: OAuth access token (Authorization: Bearer header) when an admin has connected their account; OAuth refresh token during token-refresh calls only. Connected location ID. Plugin settings being saved (chat widget selection, SMTP enable flag and configuration, SEO override fields, white-label URL, AI Pages flags). Funnel/page identifiers and the WordPress post ID they were imported into (during funnel import, refresh, and native-mode warm-up). Custom-value field keys for the connected location during the admin “sync custom values” action. Cache-purge target identifiers ( {locationId} , {wpId} ) inside the URL path when CDN purge fires; no request body is sent for cache-purge calls. Chat-widget service URL configuration is exposed to the widget loader through script data-* attributes when the chat widget is enabled. Optional funnel tracking-code download URL when LeadConnector supplies a download URL on this host during import / publish. When sent (admin-triggered server-side requests only): OAuth connect / disconnect flow (admin clicks “Connect to LeadConnector” or “Disconnect”). OAuth token refresh (background WP-Cron task leadconnector_oauth_token_refresh_cron , fired only when a connected access token is approaching expiry). Settings save on the LeadConnector admin screen. Funnel browse, import, and refresh actions (admin clicks “Import” / “Refresh” inside the LeadConnector funnels UI). Custom-value listing and sync action. SMTP enable / disable / test send actions. Reviews widget admin browsing. Admin REST proxy requests that target an allowlisted full URL on this host. CDN cache purge (see below for triggers). CDN cache-purge triggers (only when CDN_WP_ID or CDN_SITE_ID is defined in wp-config.php and an active OAuth session exists). The plugin sends an authenticated empty-body POST to services.leadconnectorhq.com/wordpress/lc-plugin/site/{locationId}/{wpId}/clear-cache on: A connected WordPress administrator clicking “Purge everything on all domains” in the admin bar. The LeadConnector settings page being saved. A public post (any post type registered with public => true , including standard post , page , WooCommerce products, and third-party CPTs) being published or updated via WordPress’s save_post hook. Auto-saves, revisions, and non-public post types are skipped. Custom-value placeholder fallback (a single front-end-render code path): when a {{custom_values.…}} placeholder is referenced on a public page and the local transient cache is cold for that key, the public renderer falls back to an authenticated read from services.leadconnectorhq.com using the admin-issued OAuth bearer that the site has stored. The fallback is a read-only lookup; no visitor data is forwarded. Visitor browser trigger: when the chat widget is enabled, the browser loads widgets.leadconnectorhq.com/loader.js with data-server-u-r-l and data-marketplace-u-r-l values pointing at services.leadconnectorhq.com ; the widget may contact those service endpoints directly. Browser requests include the selected widget configuration plus normal browser metadata (IP address, User-Agent, Referer, language headers, and any cookies the host previously set). What is not sent by PHP server-to-server calls: WordPress administrator credentials, password hashes, WordPress secret keys/salts, WordPress authentication cookies, other plugins’ data, visitor IP, visitor User-Agent, or visitor referrer. Chat-widget browser requests are initiated by the visitor’s browser and carry normal browser metadata as described above. Service: provided by LeadConnector LLC. Service terms: https://www.leadconnectorhq.com/terms2 Privacy policy: https://www.leadconnectorhq.com/privacy-policy
