Hybrid LinkPro

Cloud API or Linked Devices? Why not both.

One Polymorfa Number, both connections. Templates over Cloud API, replies over Linked Devices, without Meta's new per-reply fees from October 1.

Start building Read the guide

Connection lifecycle

Add a connection. Keep your Number.

Keep both paired. Upgrade from one connection, migrate in either direction, or use a supported downgrade when you need it.

Keep your Number. Console tier quotes show the effective time. Eligible merges preserve the survivor’s ID, customer and settings; the absorbed Number must have HMS off.

Add the missing connection. Verified QuickLink keeps the same phone and Number ID.

Explore connection setup

Meta fees

From October 1, every reply costs.

Meta now charges per service message on the Cloud API, and utility templates inside the service window stop being free. With Hybrid Link, conversation replies go out over Linked Devices.

Pay Meta only for what needs Meta. Marketing and authentication templates still go over the Cloud API. Replies and in-conversation updates use Linked Devices, with no Meta fee and no Polymorfa per-message fee.

Choose the connection per message

Smart auto routing

Send with the connection that fits.

Configure preferences through the API and use Auto to select an eligible path. Explicit choices never silently switch connections.

Send an approved template. Order updates use Official API. Applicable Meta charges are separate.

Keep a conversation moving. Supported Linked sends have no Polymorfa per-message fee. Number service and transport eligibility still apply.

Apply your routing rules. Team, project and Number preferences shape Auto. Child rules cannot widen parent restrictions.

Consent, known recipient identity, readiness, funding and BanSafe still apply.

Compare Number tiers

Identity and context

Keep the conversation together.

Correlate observed identities across both connections, preserving the message, provider references and entry point.

Keep retained history organized. Proven mirrors share a message ID. Enabled HMS follows region and retention rules, without automatic history import.

Understand message IDs

Keep the ad context. When the Linked Devices copy is unavailable, the Official API event can still supply the message and referral. An observed, routable Linked identity enables eligible follow-up in the same conversation.

Explore message webhooks

In your code

Send once. Follow the outcome.

Use the shared conversation ID and transport auto. The response names the connection and the operation.

Sending guide SDK docs

send.ts

const { data } = await messaging.messages.send("sales", {
  transport: "auto",
  conversation: { id: "739182640518203" },
  content: { text: "Here are the sizes." },
});

data.transport;     // "linked_devices"
data.routingReason; // "project_rule"

API surface

The Hybrid Link API.

Routing rules for the team, project and Number, with revision guards. Child rules cannot widen parent restrictions.

Hybrid Link docs

Sending

POST/messaging/{session}/messages/sendSend with transport auto or a fixed connection
Eventmessage.ackDelivery and read, per connection
Eventmessage.receivedMessages from both connections in one conversation

Routing

GET/messaging/routing/hybridRead a team, project or Number rule
PUT/messaging/routing/hybridSet a rule with a revision guard
GET/messaging/{session}/hybrid-linkThe Number's connection state
PUT/messaging/{session}/hybrid-linkPause or resume Hybrid sending

Connections

GET/platform/projects/{projectId}/hybrid-merge-candidatesNumbers that can merge into Hybrid Link
GET/platform/operations/{operationId}/transitionsFollow a connection change

Start with a free number

Your first real number is free. Add more numbers on Pay-As-You-Go.

Start building See pricing