Skip to main content
An Official API (Cloud API) number can be connected to more than one platform at the same time: D-API and a CRM, a chatbot, another API. To Meta, each platform is a partner (an app). This page explains how they coexist without getting in each other’s way.
Summary in three sentences. Both partners can be on the number at the same time, but each conversation has a single owner who replies. The business that owns the number decides who owns what, in Meta Business Suite. D-API shows its role, receives a copy of the other partners’ conversations (standby) and, when allowed, takes over a conversation at any time.

Why this exists

Without any rule, every connected partner receives every message and every partner can reply. In practice that is a mess: two bots answering the same customer, or one partner replying to a conversation the other was handling. Meta solved this with Conversation Routing: the business defines which partner handles each kind of conversation, and Meta delivers the message only to that partner.
When a second partner joins the account, Meta may create a routing configuration automatically from the partners already there. If D-API (or the other partner) stopped receiving messages, or started getting error 131070, right after a new connection, this is why. Check the configuration in Meta Business Suite and D-API’s role.

Concepts

What each partner can do

Templates can always be sent, by any partner, owner or not. Sending a template does not change the conversation’s owner. What can change it is the customer’s reply: tapping a template button routes the conversation again through the marketing/utility entry point.

1. Find out the number’s situation

One call shows whether there are other partners and what D-API’s role is:
YOUR_CONNECTION is the connection id or the session id (cloud-…).
Response
string
The summary. One of three values:
  • exclusive: only D-API is on the account. Everything works as usual.
  • shared_without_routing: there is another partner and no routing. Both receive every message and both can reply. Configure routing to avoid duplicate replies.
  • routed: routing is active. What D-API does depends on roles and isStandby.
string[]
Entry points where D-API is the primary: customer_service (service), ctwa (Click to WhatsApp ad), marketing, utility, calls. Contains escalation if D-API is the escalation partner. Empty when D-API is primary for nothing.
boolean
true if the business granted D-API standby visibility (a copy of other partners’ conversations).
boolean
true if D-API can take over any conversation. Shortcut for roles containing escalation.
object[]
Partners (apps) connected to the account. isCurrentApp: true marks D-API.
number
How many partners besides D-API.
This route queries Meta live, and Meta rate-limits it. Use it on settings screens or after a 131070 error. Do not call it before every send.

2. Configure routing in Meta Business Suite

The configuration belongs to the business that owns the number and only exists in Meta’s interface. No partner (D-API included) can configure it via API.
1

Accept the terms

Standby, escalation and owner changes require the business to accept the Meta Business Agents and Platform Terms of Service. Without it, only basic routing works.
2

Open conversation routing

In Meta Business Suite, open the WhatsApp account settings and look for Conversation Routing. It can be configured for the whole account or for a specific number (the number’s configuration wins).
3

Pick the primary for each entry point

For each of the five entry points, pick the partner that handles it. For marketing and utility there is a “Route to sender” option: the customer’s reply goes to the partner that sent the template.
4

Pick the escalation partner (optional)

At most one. It can take over any conversation.
5

Grant standby visibility (optional)

Off by default. Select the partners that should receive a copy of the conversations they don’t own.
6

Save and check

Call GET /routing and confirm D-API’s role is the expected one.

3. Use cases

Scenario. The business uses another platform day to day and wants D-API ready to take over if it fails, without interfering with it.Meta Business Suite configuration:GET /routing result: situation: "routed", roles: ["escalation"], isStandby: true.Day to day:
  • The other partner receives and answers everything, as usual.
  • D-API receives a copy of everything through the webhook, with is_standby: true: customer messages and what the other partner sent (fromMe: true). The history in the dashboard is complete.
  • D-API flows, automations and AI agents do not run on these copies.
  • D-API can send templates whenever it wants.
When the other platform goes down, D-API takes the conversation in one of two ways:
  • Explicit: call take.
  • Implicit: send a regular message through D-API. Meta transfers the conversation immediately, and the other partner is told it lost it.
After taking over, that customer’s next messages reach D-API as regular messages (no is_standby), and flows and automations run again.To give the conversation back to the other partner, use pass with targetRole: "customer_service", or release to let the customer’s next message decide by the configuration.
Because D-API is the escalation partner, any service message it sends (via API, the dashboard, a scheduled flow) takes the conversation from the other partner. If your integration must not take conversations, send only templates while the other platform is up.

4. Change a conversation’s owner

One route, three actions. Always for one conversation (one customer).
string
required
take, pass or release.
string
required
The customer’s phone number. Any formatting or a JID (5551999999999@s.whatsapp.net) is accepted.
string
Only with pass. Which entry point receives it: customer_service, ctwa, marketing, utility, escalation or ai_agent (Meta Business Agent, if enabled on the account). Without it, pass goes to the escalation partner.
string
Free text, up to 2000 characters, delivered to the partner that receives the conversation.

Take over (take)

D-API takes the conversation from whoever owns it. Only works if D-API is the escalation partner.
Response
Meta notifies the partner that lost the conversation.

Hand over (pass)

D-API, as the owner, hands the conversation to another partner.
pass is rejected if the conversation is idle, if D-API is not the owner, if the chosen entry point has no primary, or if the target already owns it.

Release (release)

D-API, as the owner, makes the conversation idle. The customer’s next message is routed again by the business’s configuration. Releasing an idle conversation does not fail.
release triggers no webhook for anyone: there is no new owner until the customer writes again.

Errors

Error example

5. Webhooks

Copies of other partners’ conversations: is_standby

Copies arrive on the same events as always, with one extra field: is_standby: true. Regular messages do not have the field.
Customer wrote in the other partner's conversation
The other partner sent a template
Templates sent by the other partner arrive with type: "template" and the text [Template name]: parameters in message. Interactive messages arrive with type: "interactive" and their body text.
Do not reply to messages with is_standby: true. The conversation belongs to another partner: the reply is rejected with 131070 or, if D-API is the escalation partner, it takes the conversation from the other partner.

Owner change: conversation.control_changed

Sent when a conversation changes owner involving D-API:
  • type: "control_passed": another partner handed the conversation to D-API. D-API is now the owner (is_owner: true).
  • type: "control_taken": the escalation partner took the conversation from D-API. D-API is no longer the owner (is_owner: false).
string
control_passed or control_taken.
boolean
true: D-API became the conversation’s owner. false: it no longer is.
string | null
Role of the previous owner (customer_service, ctwa, marketing, utility, escalation, ai_agent).
string | null
Role of the new owner.
string | null
Text sent by whoever made the change.
string | null
Conversation summary generated by Meta, when it sends one (only on control_passed).

6. Sending in another partner’s conversation: error 131070

If D-API tries to send free-form text or media in a conversation it doesn’t own (and it is not the escalation partner), Meta refuses. The send route responds:
The message text is in Portuguese. Match on 131070 in the text to detect this case.
What to do:
  1. Need to reach the customer now? Send a template.
  2. Is D-API the escalation partner? Take over with take (or the send itself takes over, with no error).
  3. Otherwise, ask the owning partner to pass the conversation to D-API, or change the configuration in Meta Business Suite.
An idle conversation (no owner) also refuses free-form text: the customer’s next message decides the owner. To pull an idle conversation, send a marketing or utility template: if the business set that entry point to “Route to sender”, the customer’s reply brings the conversation to D-API.

FAQ

No. D-API’s role is whatever the business configured in Meta Business Suite, and it can differ per number. The business can change it at any time: make D-API primary for one or every entry point, remove standby, or remove the other partner (then routing disappears and everything is back to normal). Use GET /routing to see the current role.
Yes, on the same number and at the same time, but not in the same conversation at the same time: each conversation has one owner. Both can send templates freely.
GET /routing: otherAppsCount greater than zero and the list in subscribedApps.
No. Copies with is_standby: true go to the history and the webhook, but do not trigger flows, automations or AI agents. They run again once D-API owns the conversation.
Yes, when D-API has standby visibility: the customer’s messages and the other partner’s replies are added to the conversation history.
No. Messages sent by the other partner are not part of D-API billing. Meta bills each template to whoever sent it.
Standby copies are not forwarded to Datacrazy: its format cannot mark a message as a copy, and its automation would reply to a conversation D-API does not own.
Until it is handed over, released or taken, or until 24h without a customer message. After that it becomes idle, and the customer’s next message picks the owner again by entry point.
D-API does not register again a number that is already active on the Official API with another partner, so it does not change the two-step verification that partner set up. But Meta may create an automatic routing configuration when the second partner joins. After connecting, check the configuration in Meta Business Suite.