GatewayAPI vs Linq

Compare GatewayAPI and Linq side by side: iMessage features, channels, developer tools, pricing and compliance, checked on each provider's own site.

GatewayAPI

Danish SMS, RCS and email API with an EU-hosted setup
Starting price
0.0201 EUR per US SMS (standard route)
Free plan
Free account with test credits

Linq

iMessage, RCS and SMS API with flat monthly pricing
Starting price
$260/month (Pro)
Free plan
Hobby: $0, up to 20 contacts, used through the CLI

GatewayAPI supports 18 of the 77 features compared here, and Linq supports 63.

Where GatewayAPI is ahead

Feature comparison

FeatureGatewayAPILinq
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
SupportedVirtual long codes and short codes in 50+ countries, from 10 EUR a month
SupportedPaid lines are dedicated. Provisioned by Linq, no self-serve number API.
Shared numbers
PartialKeywords leased on a shared Danish short code (1204) for inbound SMS
SupportedFree Hobby tier uses a Shared Line, inbound-first, 20 contacts.
Bring your own number
Not listed
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
SupportedBusiness-initiated SMS and RCS sends
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
Supported
Supported
RCS
SupportedAgent setup goes through sales; RCS business messaging covers some markets only
Supported
WhatsApp
Not supportedNot offered
BetaSeparate WhatsApp API in beta. Access by request, no SLA.
Telegram
Not supported
Not supportedNot offered
Slack
Not supportedNot a channel; a Slack integration relays SMS notifications
Not supported
Email
SupportedEmail REST API with SPF and DKIM, plus email to and from SMS
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
PartialMessaging API covers SMS and RCS with automatic SMS fallback; email uses a separate API
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
Supported@onlinecity/gatewayapi-node, type-safe SDK for the Messaging API
Supported@linqapp/sdk
Python SDK
Not listedDocs show Python examples with the requests library, not an SDK
Supportedlinq-python
Other SDKs
Not listedCode examples for PHP and Java; a WordPress plugin
SupportedOfficial Go SDK.
CLI
Not listed
Supported@linqapp/cli: signup, sending, and a local webhook listener.
Webhooks
SupportedStatus events and inbound SMS and RCS messages
Supported
Signed webhooks
SupportedHMAC-SHA256 of the raw body in a Signature header (v1=...)
SupportedHMAC-SHA256, Standard Webhooks format, with replay protection.
MCP server
Not listed
Supported@linqapp/sdk-mcp with docs search and code execution tools.
Open source
Not supportedClosed platform; the Node SDK and WordPress plugin are public on GitHub
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
Not listed
Not listedThe CLI streams webhooks locally, but tests still use a real phone.
Custom channel providers
Not listed
Not listed
Event replay
PartialAutomatic retries with backoff for at least 24 hours, then the event is dropped
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
SupportedZapier and Make
SupportedLinq Blue works as a GoHighLevel messaging provider. No n8n, Make or Zapier found for the API.
CRM integrations
PartialSalesforce and Pipedrive through Zapier or Make, no native app
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
Not listed
Not supportedDocs say the Chat SDK adapter buffers streams into one final message.
Agent group chats
Not listed
Not listed
Human handoff
Not listed
Not listed
Audit logs
Not listed
SupportedDashboard Activity page plus account-change webhooks with actor and origin.
Message history API
PartialLegacy REST API returns a sent SMS by ID; the Messaging API has no read endpoints
Supported
Plans and compliance
Free plan
PartialFree account with test credits; sending is pay as you go
SupportedHobby: $0, up to 20 contacts, through the CLI.
Public pricing
Supported
SupportedPro from $260/mo. Enterprise is custom.
No per-message fees
Not supportedBilled per message
Supported
Uptime SLA
Not listedAn extended support SLA is an add-on; the site cites historical uptime above 99.99%
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
Not listed
SupportedType I and Type II, reports for 2022, 2024, 2025 and 2026.
GDPR
SupportedGDPR compliance audited yearly under ISAE 3000 and ISAE 3402
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

GatewayAPI

Pay as you go per message with no subscription; standard-route SMS costs 0.0201 EUR to the US and 0.0401 EUR to Denmark, RCS starts at 0.0410 EUR per message in Denmark, and virtual numbers start at 10 EUR a month.

Pricing model: per message, pay as you go

Source

Linq

Hobby is free with up to 20 contacts through the CLI, Pro starts at $260 a month with a 7-day free trial, and Enterprise is custom.

Pricing model: flat monthly, no per-message fees

Source

Which should you choose?

Choose GatewayAPI if you need email.

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

Frequently asked questions