Skip to content
Merulan

WhatsApp setup

What an operator supplies to connect the WhatsApp Source, and the verification the provider requires.

Connecting WhatsApp is opened by Merulan support on the operator behalf. Merulan support holds the credential. An operator who holds the material below connects in one pass.

Prerequisites

WhatsApp refuses the connection until every item holds.

  • A WhatsApp account reachable on a device that can confirm the sign-in.
  • A Merulan support request, because the WhatsApp connection is opened out of band rather than from the Console.

Credentials

WhatsApp stores the credential under the operated custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. Merulan support opens a hosted sign-in session with the vendor, and the resolved handle lands on the connection row.

Scopes

WhatsApp carries no scope list in Merulan: the aggregator account that opens the session holds the requested scopes for this Source.

Merulan declares no WhatsApp scope, so the reach of the connection is the reach the aggregator negotiated.

Verification

Support-operated connection governs the WhatsApp connection. Meta admits the aggregator rather than Merulan, so the WhatsApp connection carries the aggregator standing and no Merulan application review.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.