--- title: "HeyReach API review: per-sender pricing, nothing gated" description: "The HeyReach API, webhooks and MCP server come with the $79 Growth plan. 300 requests a minute, an X-API-KEY header, and keys that never expire." url: https://frontal.so/gtm-apis/sending-apis/heyreach-api-review updated: 2026-11-12 --- # HeyReach API review API, webhooks and MCP on the $79 entry plan Reviewed by **Frontal** *·*Updated October 2026 ## On this page 1. Pricing and plans 2. Rate limits 3. API key and access 4. Request example 5. Docs and reference 6. Video walkthrough 7. Strengths and limits 8. Verdict 9. Before you build 10. Top alternatives 11. Head to head [Visit HeyReach](https://www.heyreach.io/) **From** $79/sender/mo **Unit cost** Not sold by the unit **Billing** Subscription Per seat **Best for** API, webhooks and MCP on the $79 entry plan check-key.sh public API ``` GET https://api.heyreach.io/api/public/auth/CheckApiKey X-API-KEY: $HEYREACH_KEY # 300 requests a minute, every request on one limit # keys never expire; delete or deactivate to revoke # 429 when the minute is spent ``` 200 OK API from $79/sender HeyReach is LinkedIn automation priced per sender, and the HeyReach API is on the entry plan rather than held for an agency tier. Growth at $79 a sender a month carries the API, webhooks, an MCP server and client workspaces, so on the "who charges extra for the API" question HeyReach is with lemlist, Reply.io, Instantly and Dripify: building against it costs nothing extra. The bill is shaped by senders rather than by volume. Growth is $79 a sender paid monthly, $71 billed quarterly and $63 billed yearly. Agency is $999 a month for 25 senders, which is about $40 each and becomes the cheaper line at around thirteen accounts. Unlimited is $2,999 a month, capped at 300 senders by a fair-use policy. The API itself is small, clear and published openly: a Postman collection grouped into campaigns, inbox, LinkedIn accounts, lists, leads, analytics, webhooks and a few more, authenticated by a key in an X-API-KEY header and limited to 300 requests a minute. HeyReach also ships a hosted MCP server and a CLI, and native integrations that move leads to Instantly and Smartlead for the email half of a sequence. The rest of the category is in the [Sending APIs](https://frontal.so/gtm-apis/sending-apis) listing. ## HeyReach API pricing, plan by plan HeyReach API pricing is the sender price: the API, webhooks and [MCP server](https://frontal.so/gtm-apis/mcp-servers) are on every plan, so the only decision is how many LinkedIn accounts you run. | Plan | Price | Senders | Enrichment credits | | --- | --- | --- | --- | | Growth | $79/sender/mo, $71 quarterly, $63 yearly | One per seat | 100 per sender | | Agency | $999/mo, $899 quarterly | 25, with a 50-sender option shown without a price | 1,000 | | Unlimited | $2,999/mo, $2,699 quarterly | Up to 300 under fair use | 3,000 | | Done for you | Custom | Managed outbound with a dedicated GTM engineer | Quoted | Enrichment credits are a one-time allocation that comes with the subscription, with top-ups sold on top, rather than a monthly allowance. Whitelabel is included on Agency, and custom branding for multiple clients is $500 per add-on on Unlimited. There is no free tier; the plans start with a free trial. The crossover is at about thirteen accounts Twelve senders on Growth is $948 a month and thirteen is $1,027, against $999 for 25 on Agency. Below that line every sender is a line item at $79; above it the agency plan is cheaper even if you never fill all 25 slots. Price your real account count before the plan names. ## One limit for every request HeyReach API rate limits are a maximum of 300 requests a minute, and HeyReach is explicit that all requests are attributed to the same limit. Going over returns a 429 and an error. ### What the limit covers One pool, not one per endpoint. - 300 requests a minute across everything you call. - No separate budget for reads, writes or analytics. - A 429 HTTP status when the minute is spent. - The docs publish one figure, with no difference between plans. ### What it means for a build Pace the bulk jobs. - A lead import and a live inbox poller share the same 300. - Webhooks are the way to hear about replies without spending the limit on polling. - The LinkedIn side has its own daily safety limits per sender, set inside the product. - Back off on 429 and retry; the docs do not publish a Retry-After value. Three hundred a minute is generous for LinkedIn, where the real ceiling is how many actions a single account can safely take in a day. The API limit is unlikely to be what slows you down; the per-sender daily limits are. Built in Clay ### Building this yourself? *Start in Clay.* Clay runs a waterfall across 150+ data providers from one table, without a separate contract with each. A lookup that finds nothing costs no data credit. **150+** data providers **500** free actions a month **$0** for a miss [Try Clay](https://go.frontal.so/clay) Frontal is a Clay Elite Studio Partner. A Clay waterfall **Clay** ## How to create a HeyReach API key A HeyReach API key authenticates every request through the X-API-KEY header, and the docs say plainly that keys never expire, though they can be deleted or deactivated. The first call to make is the key check, which returns a 200 when the key works. ### Using the key A header on every request. - Send it as X-API-KEY: your-key. - The key maps requests to your organization. - Call /api/public/auth/CheckApiKey first; a 200 means it works. - Revoke by deleting or deactivating the key, since it never expires on its own. ### The MCP server and the CLI For agents rather than scripts. - HeyReach describes its MCP server as one of the first official ones from a LinkedIn outreach tool. - It connects to Claude, n8n, Clay, Visual Studio Code and Make, with setup guides for each. - The CLI is pitched at running outreach from a terminal or a Claude chat. - Neither needs custom code against the endpoints, which is the point of both. A key that never expires is convenient and is also the thing to manage deliberately. Store it as a secret, give each integration its own key so one can be revoked without breaking the rest, and make deactivation part of offboarding a client workspace. ## A minimal call The key check is the one request every HeyReach integration should make first. It takes the header and nothing else, and its documented success is a bare 200 with no body. check-key.sh curl ``` curl --location 'https://api.heyreach.io/api/public/auth/CheckApiKey' \ --header 'X-API-KEY: ' # 200 OK, no response body ``` 200 OK Body none ## Where the HeyReach API documentation lives The HeyReach API documentation is a public Postman collection rather than a docs site, and the HeyReach API docs cover authentication, the rate limit and every endpoint group on one page with cURL examples. MCP setup lives in the HeyReach help center instead. | Surface | Where | What it answers | | --- | --- | --- | | API reference | documenter.getpostman.com/view/23808049/2sA2xb5F75 | Keys, the 300 a minute limit and every endpoint group. | | MCP setup | help.heyreach.io | Connecting the MCP server to Claude, n8n, Clay, VS Code and Make. | | CLI | heyreach.io/cli | What the command line client is for. | | Pricing | heyreach.io/pricing | Senders, billing periods and credits. | The endpoint groups tell you the shape of the product: campaigns, the unified inbox, LinkedIn accounts, lists, leads and lead tags, analytics, webhooks, your network, the organization, enrichment and a blacklist. A Postman collection is easy to import and run, and harder to search than a docs site, so keep the collection open alongside your client code. The [MCP page](https://frontal.so/gtm-apis/mcp-servers) lists HeyReach's MCP access alongside the others in this directory. ## HeyReach's own integration walkthrough HeyReach publishes this on its own channel, so it is HeyReach's account of HeyReach, not ours. It is here because a rate card cannot show you the thing moving, and a few minutes of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours. [YouTube · HeyReach How to integrate HeyReach with Instantly? 4:52 · Published November 2025](https://www.youtube.com/watch?v=2v4VTMfvtX4) HeyReach's own walkthrough of its native Instantly integration: an 'Add to Instantly' step inside a LinkedIn sequence that moves a lead into an Instantly list, and the route back. It shows the two-tool LinkedIn plus email pattern HeyReach is built for. It is an integration rather than the API, and the claims about doubled touchpoints are HeyReach's. Published 19 November 2025 on [HeyReach](https://www.youtube.com/channel/UCQW6OckhMzssxlGePg1xFQQ), the channel HeyReach's own pages link to, and read on 23 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from a HeyReach page. ## Strengths and limits HeyReach puts the whole developer surface on the entry plan and prices only the senders. ### What it does well - The API, webhooks, MCP server and workspaces on every plan, from $79. - A published 300 requests a minute, on one simple pool. - Keys that never expire, in a plain header. - Native integrations with Instantly and Smartlead for the email half. - An agency plan that drops the per-sender price to about $40 at 25 accounts. - A CLI and an official MCP server for agent-driven work. ### Where it falls short - Per-sender pricing is the dear way to run a few accounts: Dripify is cheaper below about seventeen, and Agency only beats Growth from thirteen. - Above 25 senders the published ladder stops until the $2,999 Unlimited plan. - The 50-sender option has no published price. - Enrichment credits are a one-time allocation, not a monthly one. - The reference is a Postman collection rather than a searchable docs site. - No Retry-After behavior is documented for the 429. The panels split along the same line as the pricing. Everything a builder needs is included and documented, and everything that costs money is a LinkedIn account, so HeyReach is cheap to integrate and its bill grows with the number of profiles you run. ## Who should build on HeyReach HeyReach is the LinkedIn tool to build on when you run many accounts, which is the agency case it was designed for. From thirteen senders the Agency plan beats Growth, from about seventeen it undercuts Dripify's $59 seat, and at 25 it is about $40 an account. The API, webhooks and MCP server cost nothing extra at any size. For a single operator it is the opposite. At $79 a sender a month, one or two accounts cost more here than on Dripify, and the developer surface you get for it is something you may not use. Start from the account count, not the feature list. Technically it is one of the easier integrations in sending: a header, a key that does not expire, one 300 a minute pool and webhooks for replies. The work is not the API, it is pacing LinkedIn actions inside each sender's daily limits, and that is where an integration earns its keep. ## Before you build against it Four things to settle first, each one read off HeyReach's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration. Provenance ## Where the data comes from, and what you may do with it The question that arrives late and expensively is who is allowed to hold the data. These are the fields it returns, the coverage it claims and the compliance it publishes. | Provider | Fields returned | Coverage | Compliance | Redistribution | | --- | --- | --- | --- | --- | | [HeyReach](https://frontal.so/gtm-apis/sending-apis/heyreach-api-review) | LinkedIn profile, Work email | Global | GDPR DPA | Not stated | HeyReach states no redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first. Two practical notes. A compliance badge describes the vendor rather than your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And the vendor runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs. ## If HeyReach is not the answer Three providers in the [Sending APIs](https://frontal.so/gtm-apis/sending-apis) listing that solve the same problem differently. Each one is a trade, and the trade is named. [Dripify $59/user/mo annual Cheaper below seventeen accounts at $59 a seat on Pro, with the API on every plan, a downloadable OpenAPI spec and published daily caps.](https://frontal.so/gtm-apis/sending-apis/dripify-api-review) [Expandi $79/user/mo annual One plan with everything in it, $79 a seat billed annually, and 22 webhook events as the integration surface.](https://frontal.so/gtm-apis/sending-apis/expandi-api-review) [Reply.io $49/user/mo annual LinkedIn and email in one sequence, with the API on every plan and in the trial. The pick when LinkedIn is a channel rather than the business.](https://frontal.so/gtm-apis/sending-apis/reply-io-api-review) The full set, organized by the reason people leave, is on the [HeyReach alternatives](https://frontal.so/gtm-apis/alternatives/heyreach-alternatives) page. ## HeyReach against the obvious rival Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: [Dripify vs HeyReach](https://frontal.so/gtm-apis/compare/dripify-vs-heyreach) and [Expandi vs HeyReach](https://frontal.so/gtm-apis/compare/expandi-vs-heyreach). Every pairing in the directory is on the [compare hub](https://frontal.so/gtm-apis/compare). [Dripify vs HeyReach Compare Per user against per sender, and the crossover sits at about seventeen LinkedIn accounts.](https://frontal.so/gtm-apis/compare/dripify-vs-heyreach) [Expandi vs HeyReach Compare Both put everything on one plan. Only one of them lets you read the API reference first.](https://frontal.so/gtm-apis/compare/expandi-vs-heyreach) ## Calling these APIs one by one? *Run them from one Clay table.* Clay runs a waterfall across 150+ data providers from one table, without a separate contract with each. A lookup that finds nothing costs no data credit, and the free plan includes 500 actions a month. [Try Clay](https://go.frontal.so/clay) [See the sending APIs compared](https://frontal.so/gtm-apis/sending-apis) Frontal is a Clay Elite Studio Partner. What practitioners say ## Nothing worth quoting yet We searched Reddit for threads about the HeyReach API and have found none worth quoting yet. When one turns up, it goes here, and nothing on this page leans on an unquoted paraphrase. FAQ ## HeyReach API, answered **Is the HeyReach API free?** No free tier. Free trial, and senders are added one at a time. Paid plans start at $79/sender/mo. **How much does the HeyReach API cost?** HeyReach starts at $79/sender/mo. It bills per seat, by subscription. Read from HeyReach's own pricing page on 23 October 2026. **What are the HeyReach API rate limits?** 300 requests a minute, shared across every request. **How do I get a HeyReach API key?** A HeyReach API key authenticates every request through the X-API-KEY header, and the docs say plainly that keys never expire, though they can be deleted or deactivated. Requests authenticate with API key in an X-API-KEY header. Keys never expire. The current steps are in HeyReach's own documentation, which is authoritative on anything that has changed since 23 October 2026. **Does HeyReach have an MCP server?** Yes. Per workspace, from Integrations. It is listed with the others on the MCP page. Published by ## [Frontal](https://frontal.so/) Frontal is the go-to-market partner for B2B tech companies past product-market fit. It publishes this directory. Every price, tier requirement and rate limit on this page was read from the vendor's own pricing page, developer documentation or knowledge base on the date below. Nothing on it is restated from a press release or a third-party listing. Where a vendor publishes no public figure, this page says so rather than estimating. [How we checked](https://frontal.so/gtm-apis#method). Reviewed by [Kenny Damian](https://www.linkedin.com/in/kenny-damian-90aba221a/) Co-founder & Head of GTM, Frontal **Verified** 23 Oct 2026 **Sources** 4 vendor documents Read from - [heyreach.io/pricing](https://www.heyreach.io/pricing) - [documenter.getpostman.com/view](https://documenter.getpostman.com/view/23808049/2sA2xb5F75) - [heyreach.io/cli](https://www.heyreach.io/cli) - [help.heyreach.io/en](https://help.heyreach.io/en/articles/12123398-how-to-integrate-heyreach-mcp-with-claude)