Unipile vs Linq

Unipile supports 24 of the 77 features compared here, and Linq supports 63.

Feature comparison

Feature	Unipile	Linq
iMessage messaging
iMessage	Not supportedNo iMessage support	Supported
Group chats	Not supported	SupportedPro plan. Up to 31 recipients. No read or delivery receipts in groups.
Group management	Not supported	SupportedAdd and remove participants and leave a group, iMessage groups only, 3-member minimum.
Group name and photo	Not supported	SupportedSet display_name and group_chat_icon on group chats.
Mentions	Not supported	SupportedGroup chats only. Notifies iMessage recipients even in a muted chat.
Tapbacks	Not supported	SupportedSix classic tapbacks or any emoji, send and receive via reaction webhooks.
Threaded replies	Not supported	Supportedreply_to with optional part_index. iMessage only.
Typing indicators	Not supported	SupportedSend and receive, in direct and group chats. iMessage only.
Read receipts	Not supported	SupportedMark chats read and receive message.read. One-to-one chats only.
Edit and unsend	Not supported	PartialEdit text up to 5 times within 15 minutes. Delete does not unsend from the recipient's device.
Message effects	Not supported	Supported11 screen and 4 bubble effects.
Animated text effects	Not supported	Supportedtext_decorations animations: big, small, shake, nod, explode, ripple, bloom, jitter.
Stickers	Not supported	SupportedPeel emoji or images onto messages, send stickers, or place them inline in text.
Formatted text	Not supported	SupportedBold, italic, underline and strikethrough ranges, plus animated text. iMessage only.
Attachments	Not supported	SupportedUp to 10MB by URL, 100MB with pre-upload.
Live Photos	Not supported	Not listed
Rich link previews	Not supported	Supportedlink parts render as rich previews on iMessage and RCS.
Voice messages	Not supported	SupportedDedicated voice memo endpoint renders the native iMessage voice bubble.
Contact cards	Not supported	SupportedSend .vcf files as media parts.
Polls	Not supported	SupportedCreate, add options, vote and read tallies, with poll webhooks. Not as a chat's first message.
Chat backgrounds	Not supported	SupportedColor, animated or photo backgrounds, in direct and group chats.
Location sharing	Not supported	SupportedRequest, read and stop Find My shares. Live location is a $79/mo add-on on Pro.
iMessage apps	Not supported	SupportedPro plan. Cards from your own Messages extension, or Linq-hosted cards (Experiences).
Live app cards	Not supported	SupportedUpdate App Card replaces a delivered iMessage app or Experience card in place.
Sender name and photo	Not supported	SupportedContact card API sets name and photo, shared per chat via Name and Photo Sharing.
FaceTime calls	Not supported	Not supportedDocs say the API does not place or answer calls.
Delivery status	Not supported	Supportedsent, delivered, read and failed webhooks. Groups report sent only.
iMessage availability check	Not supported	Supportedcheck_imessage and check_rcs endpoints.
Focus and Notify Anyway	Not supported	Not listed
Numbers and delivery
Managed lines	Not supportedNo iMessage support	Supported
Dedicated numbers	Not supportedDoes not provide numbers; end users connect accounts they already own.	SupportedPaid lines are dedicated. Provisioned by Linq, no self-serve number API.
Shared numbers	Not supported	SupportedFree Hobby tier uses a Shared Line, inbound-first, 20 contacts.
Bring your own number	SupportedEnd users link WhatsApp, Telegram, LinkedIn, Instagram and email accounts they already own.	Not listed
Line pooling	Not listed	SupportedManaged load balancing (Pro): send without from and Linq picks and fails over lines.
SMS fallback	Not supportedNo iMessage support	Supported
RCS fallback	Not supported	SupportedOrder is iMessage, then RCS, then SMS.
Outbound-first messaging	SupportedStart new chats with one or more attendees from a linked account.	SupportedFree Hobby tier is inbound-first. Docs recommend inbound-first flows to avoid flagging.
Calls on the iMessage number	Not supportedNo iMessage support	PartialAPI forwards inbound calls on the line; outbound needs caller-ID masking via another provider.
Other channels
SMS	Not supportedAnnounced for Android phones only and not released.	Supported
RCS	Not supportedAnnounced with SMS for Android phones only and not released.	Supported
WhatsApp	SupportedUser-linked WhatsApp accounts, reached through reverse engineering rather than Meta's official API.	BetaSeparate WhatsApp API in beta. Access by request, no SLA.
Telegram	SupportedUser accounts linked by QR code, on Telegram's official API.	Not supportedNot offered
Slack	Not supportedNot offered	Not supported
Email	SupportedUsers' own Gmail, Outlook and IMAP mailboxes, with calendars on the same linked account.	Not supportedNot offered. iMessage can be sent to Apple ID email handles.
Phone calls	Not supportedNot offered	PartialAPI does not place or answer calls; it forwards inbound calls. Calling lives in the Linq Blue app.
Apple Messages for Business	Not supported	Not listedAI context page mentions it, but no product page or docs were found.
Unified channel API	SupportedOne chat and message schema for LinkedIn, WhatsApp, Instagram and Telegram; email has its own endpoints.	PartialiMessage, RCS and SMS share one API. WhatsApp is a separate API with its own keys and SDKs.
Developer tools
REST API	Supported	Supported
TypeScript SDK	Supportedunipile-node-sdk for v1; unipile-node for the v2 API.	Supported@linqapp/sdk
Python SDK	BetaOfficial SDK for the v2 beta API; installed from GitHub, not on PyPI yet.	Supportedlinq-python
Other SDKs	Not listedThe PHP SDK repository is archived; no other languages found.	SupportedOfficial Go SDK.
CLI	Not listed	Supported@linqapp/cli: signup, sending, and a local webhook listener.
Webhooks	SupportedNew messages, emails, email tracking, account status and new relations.	Supported
Signed webhooks	BetaHMAC-SHA256 unipile-signature header in the v2 beta API; v1 only supports a custom secret header.	SupportedHMAC-SHA256, Standard Webhooks format, with replay protection.
MCP server	SupportedHosted at developer.unipile.com/mcp: API reference tools plus live requests with a scoped key.	Supported@linqapp/sdk-mcp with docs search and code execution tools.
Open source	Not supportedClosed platform; the Node SDK, MCP repo and n8n node are MIT-licensed.	PartialSDKs, CLI and adapters are Apache-2.0 or MIT on GitHub. The messaging platform is closed.
Self-hosting	Not supportedHosted cloud service only	Not supportedLinq describes itself as fully managed, in contrast to self-hosted options.
Local testing	Betav2 beta dashboard test accounts trigger mock webhook events without a real account.	Not listedThe CLI streams webhooks locally, but tests still use a real phone.
Custom channel providers	Not listed	Not listed
Event replay	Betav2 beta can replay stored webhook events by API; v1 retries a webhook five times.	PartialRetries for 30 minutes; after that, re-fetch chats or ask Linq for a manual replay.
OpenTelemetry	Not listed	PartialW3C trace IDs on every response and webhook for OTel backends. No export of Linq spans by default.
No-code integrations	Supportedn8n guide and official n8n node; Make and Zapier guides in the v2 docs.	SupportedLinq Blue works as a GoHighLevel messaging provider. No n8n, Make or Zapier found for the API.
CRM integrations	Not listed	SupportedVia Linq Blue: GoHighLevel, HubSpot and Salesforce.
Built for AI agents
Agent framework	Not listed	PartialNo own framework. Maintains a Vercel Chat SDK adapter and OpenClaw and Hermes plugins.
Agent framework integrations	Not listed	SupportedLinq-maintained Vercel Chat SDK adapter, plus OpenClaw and Hermes Agent plugins.
Streaming replies	PartialNo streaming; an edit-message API (WhatsApp, LinkedIn Classic) can update a sent reply in place.	Not supportedDocs say the Chat SDK adapter buffers streams into one final message.
Agent group chats	PartialLinked WhatsApp and Telegram accounts can message groups they belong to; nothing agent-specific.	Not listed
Human handoff	Not listed	Not listed
Audit logs	SupportedDashboard audit trail of user actions, plus access logs.	SupportedDashboard Activity page plus account-change webhooks with actor and origin.
Message history API	SupportedList chats and messages, and sync a conversation from its beginning.	Supported
Plans and compliance
Free plan	Partial7-day free trial, no credit card.	SupportedHobby: $0, up to 20 contacts, through the CLI.
Public pricing	Supported	SupportedPro from $260/mo. Enterprise is custom.
No per-message fees	SupportedBilled per linked account; unlimited API calls, no per-message fee.	Supported
Uptime SLA	Not listedSecurity page shows 99.9% uptime over 24 months; no contractual SLA found.	SupportedContractual SLAs on the Enterprise plan; marketing cites 99.95%
Isolated infrastructure	Not listed	SupportedDedicated lines across 4 data centers on paid plans; Hobby uses a shared line
SOC 2 Type II	SupportedSOC 2 Type II; report on request.	SupportedType I and Type II, reports for 2022, 2024, 2025 and 2026.
GDPR	SupportedData hosted only in France; processor under GDPR; DPA on request.	SupportedDPA covers GDPR and UK GDPR, with Standard Contractual Clauses.

Checked on each provider's own site and docs on 2026-10-25. “Not listed” means the provider does not mention it.

Pricing

Which should you choose?

Choose Unipile if you need bring your own number, Telegram, email and local testing.

Choose Linq if you need iMessage, group chats, group management and group name and photo.

Frequently asked questions

• Photon vs Unipile

• Photon vs Linq
• Blooio vs Linq
• Sendblue vs Linq
• Zernio vs Linq
• LoopMessage vs Linq
• Blue Reacher vs Linq
• Chert vs Linq
• Miss Blue vs Linq
• Bland vs Linq
• BlueBubbles vs Linq