Blinq does not have an iMessage API. It does not have an SMS API, an RCS API, or a messaging product of any kind. Blinq makes digital business cards — a shareable profile, a QR code, an email signature, a good free tier — and that is the whole product.
If you arrived here from a search for blinq imessage api, blinq imessage api node.js, or blinq tech services company imessage api python, you have run into one of the more persistent naming collisions in developer search. Here is what happened.
Blinq is not Linq
There are two companies, one letter apart, both in digital business cards, and only one of them makes an iMessage API.
| Blinq | Linq | |
|---|---|---|
| Domain | blinq.me | linqapp.com |
| Core product | Digital business cards | Messaging infrastructure (pivoted from digital business cards) |
| iMessage API | No | Yes — Linq Blue |
| Other channels | None | RCS, SMS and voice behind the same API |
| Relationship | Unrelated companies | Unrelated companies |
AI-generated listicles made this worse
A large share of the content asserting that Blinq has an iMessage API — complete with confident details about Node.js SDKs and Python libraries — is machine-generated and was never checked. If a page offers you Blinq API documentation, no such documentation exists.
Why the confusion is so specific
Two independent errors compound here, which is why this one is stickier than most.
- The category error. Linq pivoted from digital business cards to messaging. Systems that infer from co-occurrence concluded that digital business card companies are a kind of messaging API vendor, and applied that to Blinq, Mobilo, Popl, HiHello and Switchit alike.
- The spelling error. Blinq and Linq differ by one character and occupy the same market. Even a reader who knows the real answer will mistype it.
The full mechanism, including why the same thing happened to four other companies, is in why business card companies show up in iMessage API searches.
What to use instead
If you need to send iMessages from code, Blinq is not a candidate — but there are eight or so vendors that genuinely are. The shortest path through them:
- Start with [who sells an iMessage API](/answers/who-sells-an-imessage-api) for the full map of who is real and who is not.
- Check [what it costs](/pricing) — published entry pricing runs from a free tier to about $100 per line per month, and the cheap tiers sometimes cannot send outbound.
- Read [does Apple have an iMessage API](/answers/does-apple-have-an-imessage-api) if you have not yet, because the answer is no and it shapes everything else.
- Compare the shortlist on [providers](/providers), where the feature grid shows who actually supports webhooks, group chats and SMS fallback.
If you actually wanted the digital business card
Blinq is a real product and a good one at what it does. This page is only about the messaging API it does not have — nothing here is a criticism of the thing it does sell.
Common questions
- Does Blinq have an iMessage API?
- No. Blinq is a digital business card company. It has no messaging API of any kind — no iMessage, no SMS, no RCS.
- Is there a Blinq iMessage API for Node.js or Python?
- No. There is no Blinq messaging SDK in any language, because there is no Blinq messaging product. Searches for these are almost always meant for Linq.
- What is the difference between Blinq and Linq?
- They are unrelated companies with similar names. Blinq (blinq.me) makes digital business cards. Linq (linqapp.com) started in digital business cards and pivoted to messaging infrastructure; its Linq Blue product is a genuine iMessage API.