July 2026 Summaries

Texting APIs enable applications to send, receive, track, and in some cases enrich messages across channels such as SMS, MMS, RCS, and iMessage, supporting uses ranging from verification codes and alerts to automated customer conversations. The guide distinguishes legacy CPaaS platforms, which offer broad carrier reach and are suited to high-volume notifications but often require teams to build conversational logic and manage variable per-message costs; iMessage point solutions, which add Apple-specific rich messaging features but tend to focus on outbound sales and marketing; and agent-native infrastructure, designed for persistent AI-led conversations with features such as webhooks, context-aware workflows, rich media, routing, failover, and low-latency delivery. It compares ten providers, including Twilio, Vonage, Bird, Plivo, Telnyx, Infobip, Sinch, Bandwidth, SignalWire, and Linq, presenting Linq as the only listed platform with native iMessage support, SOC 2 Type II certification for its iMessage API, a 99.95% SLA, and flat per-number pricing. Key procurement considerations include two-way messaging capabilities, delivery reliability, security and compliance, carrier-registration obligations such as A2P 10DLC for US SMS, pricing predictability, and development speed.

Linq has partnered with Y Combinator-backed Agentcard to let agents make purchases for users directly within messaging threads using single-use virtual cards. Organizations activate the service through the Linq dashboard, while customers link payment access through a one-time verification flow sent to their existing phone number or email handle, without requiring an app, new account, or card form. Agents create payments with merchant, amount, and currency details, then manage states such as unlinked accounts, pending user approval, and readiness to retrieve short-lived card credentials directly from Agentcard. The integration emphasizes security through cards restricted to one transaction, merchant, and amount; credentials that are never stored by Linq or its customers; explicit webhooks for approvals, declines, and revoked connections; and fraud monitoring by Agentcard. The service is available immediately, with Linq customers receiving Agentcard’s Light plan at no cost for up to 200 cardholders and unlimited cards.

Linq has added Natural as a payment rail for Agent Pay, enabling businesses to create verified custodial wallets through its admin panel and request or receive payments over iMessage. The new option operates through the existing Agent Pay API with a “natural” rail parameter, alongside the original Stripe-based settlement model, and is aimed at organizations that want to collect payments without maintaining their own merchant-of-record or payment infrastructure. After completing Natural business verification, organizations can send payment requests from phone lines they own, receive funds in Natural wallets, monitor balances and payouts through Natural’s dashboard, and continue using the same payment-success webhooks for reconciliation. The service emphasizes verified legal identities, sender ownership of messaging lines, and transaction audit trails to improve trust in text-based payment requests.

Linq presents its managed iMessage API as an alternative to building and maintaining a self-hosted iMessage integration involving Macs, iPhones, Apple accounts, custom bridge software, routing, monitoring, and anti-spam controls. The service is designed for AI agents, support platforms, sales tools, and other applications requiring native two-way iMessage conversations, with support for rich media, group chats, Tapbacks, typing indicators, read receipts, inline replies, and webhooks. It claims P95 message-delivery latency below 120 milliseconds, a 99.95% uptime SLA, encrypted data handling, signed webhooks, and SOC 2 Type II compliance, which it describes as unique among enterprise iMessage API providers. The article cites Lindy’s experience of replacing a hardware-based integration after account bans and maintenance challenges, reportedly completing migration to Linq within days. Linq uses flat subscription pricing per active phone number rather than per-message fees and offers a free sandbox for testing, while asserting that developers can begin testing within minutes and connect an AI stack in roughly 20 to 30 minutes.

Linq’s messaging API treats sending as an asynchronous process, so a successful POST response only confirms that a message has been accepted and queued, while webhooks report its eventual outcome through sent, delivered, read, and failed events. The events distinguish network dispatch from confirmed device delivery, provide timestamps for measuring latency, and include actionable failure codes for retries, protocol fallbacks, and list hygiene. Delivery and read receipts depend on the messaging protocol: iMessage and RCS can emit them, while SMS and MMS generally emit only sent or failed, requiring integrations to avoid treating missing delivery events as failures. Production webhook consumers should deduplicate at-least-once deliveries using event IDs, return responses within 10 seconds while processing work asynchronously, handle retries and out-of-order events using event timestamps, verify HMAC signatures, and pin webhook versions to prevent payload changes from breaking integrations. Proper use of these events enables accurate customer-facing status indicators, delivery-rate monitoring, fallback workflows, two-factor authentication tracking, and end-to-end debugging.

Linq has launched Agent Pay, enabling AI agents in iMessage to request and collect payments within conversations rather than redirecting users to external checkout pages. Payment requests appear as tappable cards that open an App Clip on supported iPhones, allowing users to review line items and pay with Apple Pay without leaving Messages, while other devices use a web checkout. The feature supports charging for agent access, purchases or reservations completed by agents, and prepaid wallets that agents can draw from for autonomous tasks. Developers create requests through Linq’s API, share the returned checkout URL in chat, and receive a payment-success webhook after completion. Built on Stripe Connect, Agent Pay sends funds to the business’s own Stripe account, keeps the business as merchant of record, supports Stripe-compatible payment methods, and leaves refunds and disputes to the Stripe Dashboard.

Linq has introduced a privacy tier for regulated or sensitive communications that automatically deletes message content and attachment data on fixed schedules, reducing reliance on customers to issue individual deletion requests. Ephemeral messages, configurable for specific phone numbers or an entire partner account, retain inbound and outbound content for 24 hours from creation before permanently removing message bodies, formatting, and attachment references while retaining only minimal operational pointers and deletion audit records. Ephemeral attachments similarly remove underlying file bytes and metadata after one day, while using short-lived pre-signed download URLs, generally valid for 15 minutes, rather than persistent CDN links. Both features can operate independently or together, preserve standard delivery behavior and webhooks, and permit irreversible manual deletion before expiry. Because expired content cannot be recovered and no deletion webhook or expiry timestamp is provided, Linq advises customers to treat their own applications as the system of record by securely storing any necessary content when delivery webhooks arrive.

Lindy, an AI executive assistant founded by Flo Crivello, aims to reduce routine work interruptions by managing tasks such as inbox triage, meeting notes, and follow-ups through iMessage. After early work on AI agents evolved into a no-code agent platform, the company found executive-assistant use cases were most common and launched its assistant over iMessage in February. Lindy initially operated its own iMessage bridge on Mac Minis using Apple’s private frameworks and later BlueBubbles, but the approach was difficult to maintain, dependent on specialized expertise, and unable to scale because each phone number required dedicated Apple hardware and accounts that could trigger spam enforcement under high-volume use. The company subsequently moved to Linq, a managed service offering iMessage, RCS, and SMS through a unified API while handling devices, accounts, number rotation, and anti-spam operations. The migration reportedly took several hours and allowed Lindy to focus on user-facing features such as typing indicators, message debouncing, attachments, voice memos, reply threading, and SMS fallback, while operating across multiple load-balanced numbers. The account presents the change as an example of outsourcing non-core infrastructure, reducing operational risk, and directing engineering effort toward product development.

An iMessage-native AI agent can pair its text conversation with a Live Activity in Apple’s Dynamic Island to display persistent, glanceable state that would otherwise require users to scroll through messages. BodyBuddy, an AI health accountability coach built on Linq, illustrates the pattern by keeping calorie totals, meals, and streaks updated in the Dynamic Island while coaching continues in Messages. This works because Live Activities appear when their owning app is in the background; with Messages as the foreground app, BodyBuddy’s app can maintain the Island display during a chat, unlike a conventional in-app chat interface. The backend connects Linq inbound-message webhooks and outbound replies with ActivityKit updates sent through APNs, while mapping a user’s phone number to their app account and active Live Activity push token. Developers must ensure push content matches the widget’s declared state, authenticate webhooks, manage stale or ended activities, and keep compact Island views simple while reserving details for expanded views. The approach is most useful for agents that produce accumulating or changing information, such as nutrition totals, delivery estimates, balances, points, or checklists, rather than for one-off questions whose context is already clear in the message thread.

Linq has introduced two API endpoints designed to automate line selection, load balancing, health monitoring, failover, and conversation migration for high-volume messaging. GET /v3/available_number returns the currently healthiest phone number in a customer’s pool, along with an expiring vCard link that can help recipients save primary and backup numbers, though the result is advisory rather than reserved. POST /v3/messages allows customers to send messages without specifying a sender number or chat ID, automatically reusing healthy existing chats, creating chats on the best available line, or failing over from flagged lines while optionally sending a tailored continuation message. The service selects numbers based on line reputation and recent volume, supports direct and group chats identified by recipient sets, and returns details about the selection outcome. The endpoints reduce the need for customers to manage routing tables, chat IDs, number migrations, and separate chat-creation workflows, while retaining message options such as media, links, delivery-service preferences, idempotency keys, and replies.