--- title: "LinkedIn Leads API: Read Qualified Leads with REST | traxy" description: "Read LinkedIn-sourced qualified leads, signals and engagements from traxy's REST API: keys and scopes, filters, pagination, errors, and when to use MCP." canonical: "https://traxy.ai/blog/linkedin-leads-api" last_updated: "2026-11-11" --- # LinkedIn Leads API: Read Qualified Leads with REST | traxy > Read LinkedIn-sourced qualified leads, signals and engagements from traxy's REST API: keys and scopes, filters, pagination, errors, and when to use MCP. [Home](https://traxy.ai/) [Blog](https://traxy.ai/blog) [LinkedIn Lead Generation](https://traxy.ai/blog/topics/linkedin-lead-generation) Integrations # LinkedIn leads API: read qualified leads, signals and engagements from traxy with REST Read LinkedIn-sourced qualified leads, signals and engagements from traxy's REST API: keys and scopes, filters, pagination, errors, and when to use MCP. By the traxy teamPublished Nov 10, 2026Updated Nov 11, 20265 min read ![LinkedIn leads API: read qualified leads, signals and engagements from traxy with REST — traxy blog](https://traxy.ai/assets/blog-covers/linkedin-leads-api.jpg) **In this article**[Is there a LinkedIn API to run my outreach from?](https://traxy.ai/blog/linkedin-leads-api#is-there-a-linkedin-api-to-run-my-outreach-from) [What the API gives you](https://traxy.ai/blog/linkedin-leads-api#what-the-api-gives-you) [Step 1: Create a key with the right scopes](https://traxy.ai/blog/linkedin-leads-api#step-1-create-a-key-with-the-right-scopes) [Step 2: Make your first request](https://traxy.ai/blog/linkedin-leads-api#step-2-make-your-first-request) [Step 3: Filter for the leads you want](https://traxy.ai/blog/linkedin-leads-api#step-3-filter-for-the-leads-you-want) [Step 4: Get the evidence behind a lead](https://traxy.ai/blog/linkedin-leads-api#step-4-get-the-evidence-behind-a-lead) [Step 5: Page through everything](https://traxy.ai/blog/linkedin-leads-api#step-5-page-through-everything) [Handle errors](https://traxy.ai/blog/linkedin-leads-api#handle-errors) [REST, MCP, or an integration?](https://traxy.ai/blog/linkedin-leads-api#rest-mcp-or-an-integration) [Example uses](https://traxy.ai/blog/linkedin-leads-api#example-uses) [FAQ](https://traxy.ai/blog/linkedin-leads-api#faq) [Next step](https://traxy.ai/blog/linkedin-leads-api#next-step) [Open product docs](https://docs.traxy.ai/) **If you want LinkedIn-sourced leads in your own app, dashboard or data warehouse, traxy's REST API lets you read the qualified leads in your workspace, the signals behind them and each lead's engagement history. Create an API key under Integrations > API with the scopes you need, then call https://api.traxy.ai/api/v1/customer/leads with the key as a bearer token. You can filter by ICP match, engagement type (like, comment, repost or post author), date, company, tracked profile or post, and page through results with a cursor. The REST API is for reads; use the MCP connection or integrations when you need actions or delivery. traxy itself can also run the [LinkedIn and email outreach](https://traxy.ai/linkedin-outbound) to these leads from your own connected accounts after you approve the launch.** Last checked: November 10, 2026, against traxy's [API overview](https://docs.traxy.ai/api-reference/overview) , [REST quickstart](https://docs.traxy.ai/api-reference/quickstart) , [authentication and scopes](https://docs.traxy.ai/api-reference/authentication) and [pagination and errors](https://docs.traxy.ai/api-reference/pagination-and-errors) docs. ## Is there a LinkedIn API to run my outreach from? Not from traxy's REST API: it reads your workspace data and doesn't send messages. The [API reference](https://docs.traxy.ai/api-reference/overview) lists endpoints that read your leads, their signals, tracked profiles, analytics and attributed meetings, and none that send a LinkedIn message or an email. For what LinkedIn's own APIs allow, see [is there a LinkedIn API or MCP for outreach?](https://traxy.ai/blog/linkedin-api-for-outreach) The outreach runs in traxy itself. traxy runs your entire LinkedIn GTM end to end, from finding high intent leads from social intent to enriching and researching each one, to running relevant, personalized LinkedIn and email outreach to them on autopilot. You run campaigns in the app, through trax (the traxy agent), or from the [traxy MCP](https://traxy.ai/linkedin-mcp) in Claude or ChatGPT, where the AI shows what it will do and waits for your yes in chat before anything launches or sends. Messages go out from your own connected LinkedIn and email accounts. Autopilot means the campaign runs on its own once you approve it, or you approve every message. More on [LinkedIn and email outreach with traxy](https://traxy.ai/linkedin-outbound) . ## What the API gives you traxy finds people engaging on LinkedIn with topics related to your offer and checks them against your lead criteria. The API exposes the results of that work for your workspace: Endpoint What it returns `GET /customer/leads` API-visible leads, with filters `GET /customer/leads/{leadId}` One lead `GET /customer/leads/signals` Lead signals with lead, post and tracked-profile context `GET /customer/leads/{leadId}/engagements` Engagement summaries for one lead `GET /customer/leads/counts` and `/stats` Lead counts and aggregate statistics `GET /customer/account-reports` Account-level summaries built from visible active leads `GET /customer/analytics/posts/{postId}/qualified-leads` Qualified leads for one post `GET /customer/watchlist/profiles` Tracked profiles `GET /customer/meetings` Attributed meetings The base URL is `https://api.traxy.ai/api/v1`. Endpoint pages in the [API reference](https://docs.traxy.ai/api-reference/overview) describe the public contract for each one. ## Step 1: Create a key with the right scopes 1. As a workspace admin, open **Integrations** > **API**. 2. Choose **Create key** and give it a recognizable name, such as "warehouse sync." 3. Review the scopes. Include `leads:read` for lead reads. Add `leads:contact_read` only if you need saved contact details or LinkedIn profile URLs. 4. Create the key, copy it once and store it securely. API access must be available to your workspace. If key creation is unavailable, review the role or access requirement shown in the app ([REST quickstart](https://docs.traxy.ai/api-reference/quickstart) ). Without contact permission, contact fields and profile URLs are redacted. traxy's docs advise against assuming a key can read contact data because it can read leads ([authentication](https://docs.traxy.ai/api-reference/authentication) ). Common scopes for read integrations: Scope Use it for `leads:read` Leads, signals, engagements and supported meeting records `leads:contact_read` Saved contact details and profile URLs `analytics:read` Aggregate performance and meeting analytics, and the qualified leads list for one post `watchlist:read` Tracked profiles and summaries `icp:read` Active targeting and its history A key belongs to one workspace. To read another workspace, create a key there. Don't add `workspaceId` to REST requests to switch. ## Step 2: Make your first request ```bash curl --fail-with-body \ 'https://api.traxy.ai/api/v1/customer/leads?limit=1' \ --header "Authorization: Bearer $TRAXY_API_KEY" ``` Records come back in `data`, with continuation details in `page`. An empty result means no API-visible lead matched the request, so check the workspace, filters and lead disposition ([REST quickstart](https://docs.traxy.ai/api-reference/quickstart) ). Keep keys out of browser code and source control. Revoke a key from **Integrations** > **API** when you no longer need it. ## Step 3: Filter for the leads you want `GET /customer/leads` accepts filters including: - `minIcpMatchPercent` and `maxIcpMatchPercent` (0 to 100) - `engagementType` or `engagementTypes`: `LIKE`, `COMMENT`, `REPOST`, `POST_AUTHOR` - `dateFrom` and `dateTo` (date-time) - `companyNames` and `query` - `monitoredProfileId` or `monitoredProfileIds`, and `postId`, to scope leads to a tracked profile or post - `ownerId` or `ownerIds`, for leads assigned to specific members - `disposition`: `ACTIVE`, `CLIENT` or `BAD_LEAD` (lead listing defaults to active leads) - `origin`: `agent`, `watchlist` or `all` For example, commenters with an ICP match of 70 or more since November 1: ```bash curl --fail-with-body \ 'https://api.traxy.ai/api/v1/customer/leads?engagementType=COMMENT&minIcpMatchPercent=70&dateFrom=2026-11-01T00:00:00Z' \ --header "Authorization: Bearer $TRAXY_API_KEY" ``` A score filter narrows API-visible leads. It doesn't bypass qualification, deletion, blocklist or workspace access rules ([pagination and errors](https://docs.traxy.ai/api-reference/pagination-and-errors) ). ## Step 4: Get the evidence behind a lead A lead record tells you who. For why, read the signals and engagements: - `GET /customer/leads/signals` lists signals with their lead, post and tracked-profile context. It accepts filters such as `leadId`, `postId`, `relationshipLabel` and `profileType`. - `GET /customer/leads/{leadId}/engagements` lists engagement summaries for one lead. Store the source and date with each signal. When someone on your team writes to the lead, they should reference what the person did, at the level the evidence supports. See [from a LinkedIn signal to a message you can back up](https://traxy.ai/blog/linkedin-signal-to-message) . ## Step 5: Page through everything Lists default to 50 results and accept up to 100 unless an endpoint says otherwise: 1. Make the first request without a cursor. 2. Read `page.nextCursor`. 3. Pass that exact value as `cursor` on the next request. 4. Keep the workspace, filters and sort unchanged. 5. Stop when `page.nextCursor` is `null`. Treat cursors as opaque strings. Invalid or incompatible cursors return `validation_failed`. ## Handle errors REST errors use one envelope with `code`, `message`, `status` and `request_id`. What to check for each status: Status Check `400` Input validation and supported arguments `401` Missing, expired, revoked or wrong credentials `402` Workspace access or required capability `403` Scope, role, consent or allowed origin `404` Whether the resource exists and is visible in this workspace `429` Rate limiting; follow retry guidance `503` Temporary unavailability; follow `Retry-After` when supplied ## REST, MCP, or an integration? You want to Use Read leads into your app, warehouse or dashboard REST API with an API key Work with leads and run campaigns from Claude, ChatGPT, Codex or another AI client MCP with OAuth ([MCP tools](https://docs.traxy.ai/api-reference/mcp/tools) ) Push each new qualified lead to another tool as it arrives A route to Webhook, Zapier, n8n or Clay ([routes](https://docs.traxy.ai/integrations/routes) ) REST keys don't authenticate MCP, and MCP uses OAuth rather than a key. The MCP also runs campaigns: from Claude or ChatGPT you can draft one, test it on sample leads, launch it, manage sequences and senders and answer replies, and the AI waits for your yes before anything launches or sends ([LinkedIn GTM MCP](https://traxy.ai/linkedin-mcp) ). For what MCP can do, see [what the traxy MCP server can do](https://traxy.ai/blog/traxy-mcp-server-capabilities) . For a push setup, see the [n8n LinkedIn lead workflow](https://traxy.ai/blog/n8n-linkedin-lead-workflow) . ## Example uses - **A nightly warehouse sync** that pulls new leads and signals with `dateFrom` set to the last run - **A team dashboard** that combines lead counts with attributed meetings from `/customer/meetings` - **An account view** in your BI tool from `/customer/account-reports`, sorted by the most recent signal - **A post report** that lists qualified leads for each tracked post ## FAQ ### Is there an official LinkedIn API for post engagers? This article covers traxy's API, which returns leads traxy has found and qualified in your workspace. For what LinkedIn's own APIs allow, see [is there a LinkedIn API or MCP for outreach?](https://traxy.ai/blog/linkedin-api-for-outreach) , and for its advertising APIs, our note on the [LinkedIn Marketing API 202511 sunset](https://traxy.ai/blog/linkedin-marketing-api-202511-sunset) . ### Can the traxy REST API send LinkedIn messages or emails? No. The REST API reads leads, signals, tracked profiles, analytics and meetings. Outreach runs from campaigns in the app, through trax or from the [traxy MCP](https://traxy.ai/linkedin-mcp) after your yes in chat, and sends from your own connected LinkedIn and email accounts ([LinkedIn outbound](https://traxy.ai/linkedin-outbound) ). ### Can I create or update leads through the REST API? The REST API is described as the public option for application reads. Actions go through the MCP instead: lead actions and webhook delivery with the matching scopes, and campaigns, which launch or send only after your yes in chat. ### Why are emails and profile URLs missing from my results? Your key probably lacks `leads:contact_read`. Without contact permission, contact fields and profile URLs are redacted. ### Does reading leads through the API use lead capacity? No. A person uses lead capacity once, when first delivered as a qualified lead in your workspace. Reading or exporting them doesn't count them again ([plan and capacity](https://docs.traxy.ai/workspace/plan-and-capacity) ). ## Next step Create a read-only key with `leads:read` in [traxy](https://traxy.ai/) , run the one-lead request above, then add the signals endpoint so every lead in your system carries the reason it was found. [Back to all articles](https://traxy.ai/blog) ## Keep reading [All LinkedIn Lead Generation guides](https://traxy.ai/blog/topics/linkedin-lead-generation) [Lead generation12 min read ## LinkedIn Lead Generation (2026): What It Is, Strategy, Tips and Tools for B2B What LinkedIn lead generation is, a 7-step B2B strategy, the 5 main tactics, tips, tools and metrics, plus every LinkedIn lead generation guide we publish. Updated Nov 10, 2026Read article](https://traxy.ai/blog/linkedin-lead-generation-guide-2026) [Lead generation10 min read ## How to extract comments from a LinkedIn post, and keep only the commenters who fit your ICP Four ways to extract comments from a LinkedIn post, what each returns and risks, and how to keep only the commenters who fit your ICP. Updated Nov 12, 2026Read article](https://traxy.ai/blog/extract-linkedin-post-comments) [Lead generation14 min read ## How to find leads from the people who engage with a LinkedIn company page Most company page engagers are employees, job seekers and peers. How to find the ones who fit your ICP, with the post that brought each one in. Updated Nov 12, 2026Read article](https://traxy.ai/blog/linkedin-company-page-engagers-leads) The right people are already out there. ## Find your warmest leads. _Send them personalized messages._ From relevant interest to personalized outreach. Put traxy to work. [Start your free trial](https://app.traxy.ai/signup) [Book a demo](https://calendly.com/d/cvj3-p2p-cpv/traxy-demo?utm_source=website&utm_medium=cta&utm_campaign=book-demo&utm_content=footer) 7-day free trial [traxy](https://traxy.ai/) Get the most qualified leads on LinkedIn, in real time. **Product**[Social Intent Search](https://traxy.ai/social-intent-search) [LinkedIn Social Listening](https://traxy.ai/linkedin-social-listening) [Signal-Based Outbound](https://traxy.ai/signal-based-outbound) [MCP Access](https://traxy.ai/linkedin-mcp) [Case Studies](https://traxy.ai/case-studies) [Pricing](https://traxy.ai/pricing) [DFY Outbound](https://traxy.ai/managed) **Resources**[Scoreboard](https://traxy.ai/scoreboard) [FAQ](https://traxy.ai/faq) [Guides](https://traxy.ai/guides) [Docs](https://docs.traxy.ai/) [Blog](https://traxy.ai/blog) [News](https://traxy.ai/news) [Affiliate ProgramNew](https://traxy.ai/affiliates) [Agency Partners](https://traxy.ai/agency) [Creators](https://traxy.ai/creators) [About traxy](https://traxy.ai/about) [Contact](https://traxy.ai/contact) **Legal**[Privacy Policy](https://traxy.ai/privacy-policy) [Terms of Service](https://traxy.ai/terms-of-service) [Cookie Policy](https://traxy.ai/cookie-policy) © 2026 traxy, inc. All rights reserved.