Integrate LinkedIn, email and WhatsApp accounts with software or agents. Explore LinkupAPI pricing, hosted connection, iMessage and provider limits.
Used this tool? Rate it
Used this tool? Rate it
LinkupAPI is an outreach API for software products and AI agents that connects to LinkedIn, WhatsApp, iMessage and email. Its V2 documentation describes one API for finding contacts, gathering market signals and carrying out outreach. The connected account is the channel identity on whose behalf an application acts. It is an integration for product teams, not a promise that a third-party platform permits every automated action.
The company describes the service as server-side infrastructure: no browser extension or installation is needed on the account owner's machine. Its terms identify the service provider as LINKUPAPI SAS in France and describe the intended customers as professionals, including developers and organizations. The platform connects accounts that the customer owns or is explicitly authorized to operate.
V2 groups profile retrieval, search and contact access alongside network actions for invitations and connections. Standard LinkedIn search returns at most 1,000 profiles per query, even if its interface reports a higher total.
Sales Navigator people searches accept human-readable filters or a copied URL from a search, saved search or lead list. The latter route is useful where a filter does not have a friendly parameter mapping. The documentation requires a Sales Navigator seat on the connected account for this particular capability. An application designed around this method therefore depends on both the integration and the connected account's eligibility.
The send endpoint accepts one file by link, upload or path and supports up to ten attachments through multi-file parameters. Supported audio is delivered as a voice note; LinkedIn voice notes are limited to one minute.
The product's channels include LinkedIn, email and WhatsApp through connected accounts, with iMessage presented as a separate line-based offering. The send operation's parameters depend on the connected account and channel. LinkedIn requests can be messages or eligible InMail, email is sent from a connected mailbox, and WhatsApp messages use the connected number. A user interface built on these actions needs to present the identity and permissions of the account that actually sends the message.
Webhooks provide event delivery for account and message activity. The event retrieval endpoint can return stored account events after a customer-side interruption without generating LinkedIn traffic, and the documentation specifies a 30-day event-retention period. An integrator can therefore combine event notifications with a catch-up path instead of assuming a receiving service is always online. Event retention is not the same as a promise to retain all message content indefinitely.
A hosted connection link is single-use. The backend requests a URL and sends the account owner to it through a full redirect or a new tab; the documentation says not to place this flow in an iframe. The owner then completes the channel's connection process, including applicable verification. The integrator receives the resulting account_id rather than handling the credentials entered on that hosted page.
V2 requires the x-api-key header. Action requests use POST with account_id, action and action-specific params. V2 responses follow a standardized success or error format.
The MCP server has two documented authentication paths. OAuth 2.1 uses dashboard authorization for compatible clients, while API-key authentication serves headless clients and clients without OAuth support. The vendor lists Claude, ChatGPT, Cursor, Gemini and VS Code among clients for the OAuth path. This offers a way for a compatible agent to call the same service without requiring the end user to write each REST request, while connected-account authorization and provider limits still apply.
account_id. The connection flow supports an outcome notification and a redirect, and the documentation also describes polling for the result.The terms say connections may require authentication again after a password change, provider security check or session expiry. Account status is exposed through API and webhook mechanisms, while reconnection is the customer's responsibility. The hosted link's single-use rule also means an old link is not a reusable invitation to reconnect. These details affect a multi-tenant product because each customer's provider account has its own connection state.
The company positions the MCP integration for agents that find prospects, send messages and read replies through supported channels. The Prospect Data API is described as returning people, company and job data for a product or agent. An application can combine those data actions with an outreach interface without moving an account owner's messages into a separate consumer inbox interface.
The vendor describes a recruitment workflow that sources candidates, monitors job postings and contacts people on LinkedIn or by email from an applicant-tracking system.
LinkupAPI is aimed at professional developers and organizations building outreach or data workflows. Its terms grant a personal, non-transferable and non-exclusive subscription right for internal business use and products supplied to the customer's own customers. The service is particularly relevant where a team wants to add connected-account actions to software it controls, rather than merely export a list of contacts.
LinkupAPI describes a cloud service that runs server-side. Its terms cover social and professional accounts, Gmail and Microsoft 365 or Outlook mailboxes, other SMTP/IMAP providers, and WhatsApp numbers. The site separately advertises dedicated US or UK iMessage lines as an add-on. Channel coverage should be read alongside the specific connection flow and commercial unit: an add-on line is described differently from a connected LinkedIn profile or mailbox.
The provider describes a dedicated residential or ISP IP near each account's location and says it is not shared with another account. Its terms also discuss customer-provided network routing, placing responsibility for its legality, reliability and location on the customer. This is an operational description from the vendor, not a guarantee that a third-party platform will permit automation or never restrict an account.
The publicly displayed pricing page captured on November 12, 2026 shows monthly USD prices excluding VAT. It presents a connected-account model plus a separate iMessage add-on. The examples below are the figures displayed by the vendor; checkout was not tested.
| Connected accounts | Displayed price | Example monthly bill |
|---|---|---|
| Up to 15 | $55 flat | $55 for 15 accounts |
| 16–50 | $3.70 per account | $184.50 for 50 accounts |
| 51–200 | $3.30 per account | $679.50 for 200 accounts |
| 201–970 | $3.00 per account | $2,989.50 for 970 accounts |
| Unlimited | $3,000 flat | $3,000 for 2,000 or 10,000 accounts |
The V2 documentation describes $55 for the first 15 accounts, then prices starting at $3.70 per extra account. The examples are consistent with applying each tier rate to additional accounts in that band, but the reviewed pricing text does not explicitly set out that full calculation. That interpretation is an inference from the displayed examples, not a stated billing formula.
The terms describe a connected account as a LinkedIn profile, a Gmail or Outlook mailbox or a WhatsApp number. Extra accounts are billed on the period's peak simultaneous count. Automatic upgrading can be disabled to refuse over-limit connections.
The pricing page describes the flat Unlimited offer as covering all accounts from about 970. It separately says the offer is cheaper from 974 accounts. The terms captured in the same review instead say the Unlimited plan applies from 640 connected accounts. The published documents therefore differ on the transition point; the figures are presented as stated in each source rather than treated as one consistent rule.
The pricing page lists a dedicated US or UK iMessage line at $199 per line per month, billed on the first day of the month. It describes up to 50 new conversations per day for a ready number and a three-week ramp-up for a brand-new number. Once a contact replies, the conversation no longer counts against the daily new-conversation quota. The page also lists 1,000 different contacts per month per line, including ongoing conversations.
The terms describe a seven-day first-subscription trial for per-account plans, once per customer and with a valid payment method. Unless cancelled during the trial, the first billing period starts automatically. A first payment without trial has a three-day refund window only if there has been no billable use. The terms describe a separate three-day request for the first post-trial charge.
Plans are prepaid and normally renew monthly unless checkout states otherwise. Dashboard cancellation takes effect at the end of the current billing period, which remains due. Adding accounts takes effect immediately and is billed at the next renewal without pro rata; reducing the quantity takes effect at renewal without a refund or credit for the current period. The account quantity cannot fall below the plan minimum or the number currently connected.
The terms explicitly exclude email-enrichment endpoints from per-account plans and charge those endpoints in credits. One-time pack credits last twelve months and unused credits expire without a refund. Optional automatic top-up charges a new pack when the configured balance threshold is reached. Credit-based subscriptions instead renew their included credits each billing period. Unused credits do not roll over or convert unless a plan expressly includes rollover. The pricing page also describes connected-account usage as having no credits or per-call fees.
Unipile is another API vendor to examine when integrating communication channels into a product. It describes a unified API for messaging, email and scheduling. It offers a secure HTTPS REST API with a unified schema or SDKs. Scheduling is a concrete comparison point when a product needs to integrate calendar activity alongside communication. The vendors publish their own channel coverage, pricing and permissions; those details are not determined by the shared word “unified”.
The service can only act through accounts the customer owns or is explicitly authorized to operate. Its terms say external providers have their own policies and may verify, restrict or suspend accounts. LinkupAPI does not guarantee every provider permits automated activity, and a provider restriction does not itself entitle the customer to a refund under those terms.
The vendor describes API usage on connected-account plans as unlimited, subject to provider limits, technical rate limits and credit balances for email enrichment. Account-protection mechanisms such as cooldowns and revoked-session detection may delay or pause activity. The best-practices document calls its published limits conservative recommendations and warns that exceeding provider limits can produce HTTP 429 or 500 errors. These are distinct from the subscription's account-count limit.
Standard plans do not include service-level commitments or warranties according to the terms; custom written arrangements may provide them. Website availability figures are described in the terms as measurements of a past period. The service is provided on a best-efforts basis without a guarantee of uninterrupted or error-free operation. A historical percentage on a marketing page is therefore not the same as a contractual service-level commitment for a standard plan.
Email addresses returned by enrichment endpoints come from public sources and third-party providers, without an accuracy or deliverability guarantee. The terms also prohibit reselling those addresses as a standalone dataset. A connected-account outreach workflow and a standalone dataset business have different permitted-use boundaries under the published terms.
The terms require a valid legal basis for contacting recipients. They require customers to identify senders accurately. Customers must honor opt-out requests promptly. Account owners must authorize connections and customers remain responsible for actions made on their behalf.
The platform's privacy policy describes processing connected-account authentication data, account identifiers and status, sending-health information, and message content where connected inbox features are used. The terms say passwords entered during connection are used once and are not written to the database, except that SMTP/IMAP app passwords are stored encrypted. OAuth connections retain revocable encrypted tokens.
The privacy policy says personal data is not sold, and content of connected accounts is not used for advertising, unrelated profiling or training artificial intelligence or machine-learning models. That statement is limited to the provider's policy and the connected-account content it describes. It does not establish how a customer's own application or every connected provider processes data.
The policy says invoices may be retained for up to ten years. API logs may be kept for up to twelve months. Connection tokens are kept until removal, deletion, revocation or expiry. Message data is kept only as needed for the feature and no longer than the associated API-log retention period. Disconnecting via the API or dashboard deletes stored credentials and tokens. The policy says account deletion requests are honored within thirty days, subject to legally required retention.
The terms distinguish roles for the customer's outreach data: customers act as controllers and LinkupAPI as processor for personal data processed through the API. A data processing agreement is available on request and, according to the terms, applies from the first personal-data transmission whether or not a copy is countersigned. These statements describe the published contractual allocation, not an independent legal conclusion about every integration.
No. The terms permit connecting accounts the customer owns or that their owners have explicitly authorized the customer to operate.
The terms say email-enrichment endpoints are billed in credits and are not included in per-account plans.
The privacy policy says disconnecting an account through the API or dashboard deletes its stored credentials and tokens.