Blog
- Changelog
UnifyPort API Update: Conversation Labels, Contact Messages, and Request Tracing
The UnifyPort API adds conversation labels (4 endpoints), a contact/vCard message type, request_id tracing with X-Request-Id headers, three new developer tools, and real webhook payload samples — plus a cleanup that removes two undocumented fields.
Read more → - Comparison
Telegram Bot API 10.1 Just Shipped Rich Messages — Here's What It Changes (and Doesn't) for Inbound Teams
Telegram's Bot API 10.1 adds tables, inline media, math formulas, and streaming to bot messages. It's a major outbound upgrade — but it doesn't touch how you receive messages. Here's what matters if your team runs inbound across multiple platforms.
Read more → - Guide
X Banned Automated DMs in 2026 — How Inbound Support Teams Still Receive and Route Them
X's 2026 rules prohibit auto-DMs and bulk programmatic outreach, and the API meter now runs per read. If your team only needs to receive DMs and mentions, here's why the crackdown doesn't apply to you — and how to route inbound messages without sending a single automated DM.
Read more → - Comparison
TikTok Opened Commerce APIs to Third Parties — But Your DMs Are Still Locked in Seller Center
TikTok's API ecosystem now covers content posting, order management, product catalogs, and campaign analytics. The one endpoint missing? Receiving a buyer's DM. Here's how TikTok compares to the other five major messaging platforms — and the path that exists today.
Read more → - Case Study
How a 2-Person Agency Monitors X DMs and Mentions Without Paying X's Per-Read API Fees
A two-person social media agency managed X accounts for four clients using the official API. When X switched to pay-per-use pricing, their polling-based monitoring turned every 30-second check into a billable read. Here's what happened to their costs — and how they eliminated the meter entirely.
Read more → - Comparison
WhatsApp's July 2026 Rate Card Lands — What Changes for Teams That Only Receive Messages
Meta's updated per-message rates take effect with July 2026 billing. Marketing costs rise in four markets, six countries get new dedicated rates, and service conversations stay free. Here's what the numbers mean if all you do is receive.
Read more → - Guide
What Countries Use LINE? Official Account Limits and Options Outside Japan, Taiwan, and Thailand
Looking for a list of countries that use LINE app or wondering what countries use LINE for customer messaging? LINE users are global, but Official Account verification is limited to Japan, Taiwan, and Thailand. Here are the paths for everyone else.
Read more → - Tutorial
I Had Cursor Build a Telegram-to-Slack Message Relay by Pointing It at the Webhook Docs
A build log: feed the UnifyPort webhook reference to Cursor and have it scaffold a Telegram-to-Slack relay in Node.js — signature verification, Slack Block Kit formatting, and multi-channel forwarding — without registering a Telegram bot.
Read more → - Tutorial
I Had Claude Code Build an X DM and Mention Monitor — Without Touching X's API
A build log: point Claude Code at the UnifyPort webhook reference and have it scaffold an X DM and mention monitor in Node.js — signature verification, structured logging, and Discord alerts — without paying X's per-read API fees.
Read more → - Guide
WhatsApp's BSUID Migration Starts July 7 — A Five-Point Checklist for Inbound-Only Teams
Meta is replacing phone numbers with Business-Scoped User IDs in WhatsApp webhook payloads. Here's a checklist of what breaks, what doesn't, and which teams can skip the migration entirely.
Read more →