Linq iMessage API pricing
Not published. Per line with no metering, sold through a sales conversation.
The tiers
All plans
Not publishedper line, no per-message billing
- iMessage, RCS, SMS and voice behind one API
- SOC 2 Type II (vendor claim)
- Group chats, tapbacks, voice notes, typing indicators
- A sandbox before you contract
- GoHighLevel integration
Catch You cannot see a price without talking to someone, and setup fees are reported.
Costs that are not on the pricing page
- Reported setup fees, which put it out of reach for the smallest operations.
- The sales cycle itself — for a business that wants to launch this month, that is a real cost.
Linq is the enterprise-shaped vendor in the category, and its pricing reflects that: nothing published, no self-serve, and a sales conversation before you learn a number.
What you get in exchange is the only SOC 2 Type II claim in the category and four channels behind one API. If a security review is what is blocking your purchase, that combination is genuinely hard to find elsewhere — the detail is here.
If you found Linq by searching for Blinq
You are not alone, and they are different companies. Linq (linqapp.com) sells the iMessage API; Blinq (blinq.me) makes digital business cards. The full explanation.
Linq also publishes a GoHighLevel integration, which makes it one of the few realistic answers to 'the best iMessage API for GHL' — see CRM integration and best iMessage API for CRM.
The iMessage product itself is branded Linq Blue; if that is the name you were searching for, the Linq Blue page covers what it does and how it relates to Linq.
Where these numbers come from
Linq publishes no pricing. Everything here is drawn from Linq's own product pages and public reporting; the setup fee is reported rather than published.
Best value for
Teams with a procurement process, a compliance review, or volume that justifies a negotiation.
