Use the same recorded evidence and governed actions from the dashboard, REST or your AI agent.
List and update leads, tags, notes and statuses. CRM resources cover companies, pipelines, stages, deals, tasks and saved filters. Bulk actions use bounded batches and explicit confirmation where required.
Read connected integrations and synchronize supported leads or deals through their existing drivers. An integration being listed is not evidence that a particular synchronization succeeded.
Manage business profiles, approved offers and sales playbooks. Website imports produce material for review, not approved facts or automatic publication. An unapproved business returns business_review_required when used for a post.
Opportunity scans produce recorded candidates. Review their evidence, suggested reply and delivery state before deciding to send. Enabling recurring checks, sending and retries retain confirmation and governance requirements.
Save a LinkedIn source as inspiration, retrieve supported source text through the selected executor and inspect the processing result. Source retrieval and analysis are separate states.
Content-post and audience-ICP resources report recorded evidence, coverage and missing data. Engagement is not revenue or proof of buying intent. Revenue results depend on configured, source-backed conversion integrations.
Upload actual image bytes or supported file inputs first, then schedule using the returned owned media references. PDF lead-page uploads can be delivered privately; multiple files can form a package.
Cloud publishing currently supports personal posts with at most one image. Unsupported company or multi-image schedules are refused before uploading to LinkedIn. A separate post-draft lifecycle is not implemented.
API timestamps use ISO-8601 with an explicit timezone offset; storage is UTC. The composer displays the profile timezone and converts on save. Reused confirmed image uploads must belong to the same profile and source.
Search, feed, enrichment, posts and engagement are subject to their verified adapter and profile readiness. A request accepted by the API can still be blocked before LinkedIn execution.
Person enrichment returns supported visible profile sections with explicit coverage. It does not promise expanded history. Inspect capability and job results rather than inferring full coverage from a connected profile or a declared endpoint.
Every cap, limit, timeout and tool name on this page is read from the running product when the page loads. If the software changes, this page changes with it.