LinkedIn + your AI assistant · powered by LeadAdapter
You already have content records in LeadAdapter and want a useful editorial review without copying every stored post by hand.
Made for: Content coordinators
Real tasks need a LeadAdapter account. Connect LinkedIn too when your task needs fresh LinkedIn activity.
Paste this into a coding assistant that can open project files and run commands, such as Codex, Claude Code or Grok Build. You do not need to understand the code first.
Help me use this project: https://github.com/jannikco/linkedin-content-api
I'm not a programmer. My goal is: Understand the content records already stored in your
workspace.
Read the project instructions and set it up in a new folder without overwriting my work.
Guide me through LeadAdapter and its private key setup; never ask me to paste secrets into
this chat. Run a documented sample-data demo if available, then help me get a first small
result from my connected app. Explain the result in plain English. Ask before changing
records, sending messages or publishing anything.
Show the stored content posts relevant to the review I describe.
Summarize the returned records for a content review. Do not claim to publish or scrape new
posts from this example.
Turn the stored posts we reviewed into a concise content-review brief with themes and
ideas for our next editorial meeting.
flowchart LR
A["Ask your AI"] --> B["Connect LeadAdapter"] --> C["Understand the content<br/>records already…"] --> D["Review together"]
- Open LeadAdapter setup and sign in or create your account.
- Connect a LinkedIn profile if your chosen task needs fresh LinkedIn activity.
- Create the product API key through the official setup, add it privately to your AI project's environment, and ask your AI to try a small read.
What to expect: You need one LeadAdapter API key and the workspace access required by the task. LinkedIn operations also depend on the connected profile, consent and available tools. Work that is queued stays pending until a real result is returned.
Add your LeadAdapter key privately in your project settings. Keep keys out of chat and public repositories.
- Explore the LinkedIn API
- Use LinkedIn through an AI assistant
- Build with the JavaScript / TypeScript client
Technical reference: installation commands, exact capabilities and troubleshooting
Use your stored LinkedIn content as a source for sales and content workflows.
Read content records already captured in LeadAdapter and connect them to your reporting, review or repurposing pipeline. The broader platform also offers scheduled publishing, inspiration and engagement workflows.
Create your LeadAdapter account · See plans and pricing · API documentation · Full API reference
Download SDKs and the agent kit from GitHub Releases.
Use this API from Claude Code, Codex or Grok Build in your current coding session. Install the skills into the project where you are building:
node lib/cli.mjs agents install --client codex --scope project --project /path/to/your/project
# Replace codex with claude or grok for that client.No additional AI model key is needed. Live LinkedIn operations use your LeadAdapter API key and connected account permissions. Installation never writes credentials or overwrites conflicting files.
Ask your agent: “Research B2B software founders, produce a shortlist with evidence, and wait for my review before adding anyone to CRM.”
node lib/cli.mjs workflows research-to-crm --fixtureThen follow the research → review → CRM cookbook for authorized live reads and reviewed CRM handoff. capabilities.json and llms.txt provide concise machine-readable discovery. The SDK keeps its raw request API alongside task-level resources. Five runnable task recipes are included in examples/: people research, post engagers, profile enrichment, reviewed CRM handoff and existing CRM sync. Run each without flags for a plan; --fixture uses synthetic receipts. Live mutation recipes require explicit approvals and caller-supplied stable idempotency keys.
- Feed stored content into an editorial review tool.
- Connect a campaign dashboard to known post records.
- Use content context when researching relevant engagement or planning new posts.
Built for: Content operations teams, reporting tools and builders of editorial assistants.
Create or sign in to LeadAdapter, choose an owned workspace, complete required onboarding, and create a workspace API key under Settings → API keys. The only service credential required by this repository is LEADADAPTER_API_KEY.
Use a key with api:read for these examples. Fresh LinkedIn research needs a connected profile, supported execution access and required consent; your plan’s allowances apply. For a workspace with multiple profiles, add the documented profile_id to select one.
Read stored content records. Do not interpret stored content access as universal access to every LinkedIn post or a separate comprehensive analytics API.
export LEADADAPTER_API_KEY="YOUR_WORKSPACE_API_KEY"curl --fail-with-body --silent --show-error \
"https://leadadapter.com/api/v1/content-posts?limit=10" \
-H "Authorization: Bearer $LEADADAPTER_API_KEY" \
-H "Accept: application/json"The response uses LeadAdapter’s envelope: ok, data, governance context and request/action identifiers where available. Inspect the actual response; the pinned schema intentionally does not invent a universal lead, profile or search-result shape.
Node.js 22+ includes fetch; no package installation is needed for this HTTP example:
const response = await fetch("https://leadadapter.com/api/v1/content-posts?limit=10", {
headers: {
Authorization: `Bearer ${process.env.LEADADAPTER_API_KEY}`,
"Accept": "application/json"
}
});
const receipt = await response.json();
if (!response.ok || receipt.ok === false) {
throw new Error(receipt.error?.code ?? `HTTP ${response.status}`);
}
console.log(receipt); // Inspect the returned data or queued-job receipt.This repository focuses on one API workflow. Your LeadAdapter account also provides the following documented API surfaces; account access, adapter support and operation prerequisites apply.
| Capability | Build this | Documented API routes | Execution considerations |
|---|---|---|---|
| People and post discovery | Research prospects and relevant conversations | POST /linkedin/searches/peoplePOST /linkedin/searches/posts |
Fresh retrieval needs a connected, supported executor. |
| Company research | Build account context and inspect known company pages | POST /linkedin/searches/companiesGET /linkedin/companiesPOST /linkedin/company-enrichments |
Company-voice operations require the relevant page-admin rights. |
| Profile enrichment | Add visible professional context to selected leads | POST /linkedin/profile-enrichments |
Allowance, profile-view budget and returned coverage apply; email availability is conditional. |
| Post engagement | Research the people engaging with a selected post | POST /linkedin/post-engager-requests |
Results depend on what the connected account and adapter can retrieve. |
| Leads and export | Read, qualify and move captured lead data | GET /leadsGET /leads/export |
Workspace-scoped data; pagination is explicit. |
| Native CRM | Work with companies, pipelines, stages, deals and tasks | GET /crm/{entity}POST /crm/{entity}GET /crm/{entity}/records |
Write scopes and entity-specific inputs apply. |
| Stored content and publishing | Connect editorial review and scheduled publishing | GET /content-postsGET /scheduled-postsPOST /scheduled-posts |
Queued or scheduled work is distinct from confirmed publication. |
| Messages and connections | Build reviewed conversation and connection workflows | GET /messagesPOST /linkedin/messagesPOST /linkedin/connection-requests |
Outbound actions remain capped, permissioned and subject to applicable approval. |
| Engagement actions | Prepare relevant comments and reactions | POST /linkedin/commentsPOST /linkedin/post-reactions |
Writes require the appropriate scope and governance acceptance. |
| Comment-to-lead workflows | Connect a comment keyword to a controlled follow-up process | GET /automationsPOST /automations |
Supported triggers are comment_keyword and any_comment; DM prerequisites and limits apply. |
| Lead pages and tracked links | Connect campaigns with lead capture and tracked assets | GET /lead-pagesGET /links |
Publication and asset management are separate governed operations. |
| Approvals and audit | Review proposed actions and understand execution decisions | GET /approvalsPOST /approvals/{approval_id}/decisionsGET /actions |
Approval does not override caps or unavailable capabilities. |
| Webhooks | React to supported lead, comment, message and approval events | GET /webhooksPOST /webhooksGET /webhooks/{id}/deliveries |
Configure subscriptions and validate signed deliveries in your receiver. |
| Sales intelligence | Connect research with business context and reviewable opportunities | GET /signalsGET /sales-opportunitiesGET /business-context |
Availability follows the account’s configured features and existing records. |
| Operation ID | HTTP route, relative to /api/v1 |
Required scope |
|---|---|---|
list_content_posts_get |
GET /content-posts |
api:read |
This is a focused API recipe, currently maintained as an example. It uses existing LeadAdapter endpoints; it does not add a separate LinkedIn backend. Use the API reference for complete inputs, limits and operation behavior.
Stored workspace data can return immediately. Fresh LinkedIn retrieval or outbound work may return a job receipt, including job_id, instead of a completed result. When a job is returned:
- Keep its identifier and the request’s idempotency key.
- Poll
GET /api/v1/jobs/{job_id}with the same workspace key. A documentedwait=truecan hold the read for up to25 seconds. - Inspect the terminal status and result/error:
done,failedorcancelled.queuedandleasedare still in progress.
export JOB_ID="REPLACE_WITH_RETURNED_JOB_ID"
curl --fail-with-body --silent --show-error \
"https://leadadapter.com/api/v1/jobs/$JOB_ID?wait=true" \
-H "Authorization: Bearer $LEADADAPTER_API_KEY" \
-H "Accept: application/json"An accepted request, an approved action and confirmed LinkedIn delivery are separate states. Do not report successful delivery from a queue acknowledgement.
- One workspace key, explicit scopes. Use
api:readfor the documented reads, and grant write access only for the operations your application needs. Store keys server-side; do not place them in browser bundles, commits or issue reports. - Connected-account execution. Browser-mode work uses the user’s connected browser. Supported consented cloud operations can run independently of Chrome. Availability is checked per operation; an API route does not grant unrestricted LinkedIn access.
- Governed actions. Workspace/profile caps, pacing, do-not-engage rules, account permissions and required approvals still apply. Some operations support
dry_run; check the operation’s schema before sending it. - Explicit retries. Operations requiring
Idempotency-Keyinclude fresh-data POST reads as well as writes. Reuse the same key and payload for the same logical request. Resolve uncertain outcomes before issuing a new request. - Useful errors. Handle permission/capability refusals, validation errors and429 pacing responses. Preserve request identifiers for support and follow any returned retry guidance.
This repository publishes a runnable API recipe under MIT. LeadAdapter’s hosted application, connected-account execution, governance, data storage and commercial service remain private. The public code does not include the service backend or a self-hosted substitute for a LeadAdapter account. This is an independent LeadAdapter integration, not an official LinkedIn API or LinkedIn-endorsed SDK.
- Activate this workflow in LeadAdapter — the selected project and repository campaign stay with your signup.
- Plans and pricing — check current feature access and allowances before production use.
- TypeScript SDK, Python SDK and MCP server.
- API quickstart, complete reference, MCP guide and public OpenAPI.
- Integration directory.
This code is checked with contract fixtures; the MCP artifact also tests stdio tools/call. These checks establish client behavior, not live LinkedIn provider execution or conversion outcomes. See integration.json and SHA256SUMS for the recorded artifact evidence. The source contract is LeadAdapter’s public OpenAPI.
For a reproducible client bug, open a repository issue with the operation ID and a sanitized request identifier. For account access, plans or execution availability, use LeadAdapter’s in-app support. Never include API keys, personal lead data or session material.