LunaDocs

Loading search...

PortuguêsSign in to the console
On this page

Coming from another official partner (360dialog, Gupshup)

Use with AI

If you already run customers through another official partner, the model is familiar: the business owns the WhatsApp Business account, the number is on Meta’s Cloud API, and you connect a customer through a Meta flow. What changes are the names of things, the webhook and how Meta gets paid. This guide maps them and says what to do with a number that is already at the other partner.

The API reference carries each route’s contract. The other partners’ columns describe, in our own words, what each one’s public documentation shows; if something changed there, their documentation holds.

What changes and what stays the same#

  • Stays the same: your customer keeps owning the WhatsApp Business account (the WABA) and their own payment method at Meta. Luna owns none of that.
  • How Meta gets paid changes. Luna is a Tech Provider and has no line of credit with Meta, so there is no wallet, balance or top-up. Each business pays Meta directly, and Luna only shows each number’s usage in GET /v1/usage. You pass that value on to your customer however you see fit, outside Luna.
  • There is no “client” or “app” object. Your customer is the externalId, a label you put on the key, the connect link and the endpoint, and which comes back in every event. The instance is the number.
  • The webhook changes. One endpoint for the whole account (or one per customer with externalIds), signed delivery, order preserved within each conversation and an event_id to deduplicate. There are no custom headers on the call: the delivery’s authentication is the signature. See Receive events.

Mapping by partner#

If you come from 360dialog

360dialogLuna
A key header, one key per channelAuthorization: Bearer hlsn_.... One key per customer, with externalId and profile: "agent".
Send a messagePOST /v1/messages: asynchronous 202 and Idempotency-Key.
Register the webhook URL per channel, with headersPOST /v1/webhooks/endpoints with url, eventTypes and externalIds. No custom headers; the signature is X-Luna-Signature.
List clientsThere is no “client” object: the externalId is your customer.
List channelsGET /v1/numbers, with the externalId, state and canSend filters.
Create a channel’s keyPOST /v1/api-keys with externalId.
Integration address and a redirect with the client and channelsPOST /v1/onboarding/links with redirectUrl, which receives status and numberId in the query. The link is valid for 72 hours. See Connect a number.
Channel created eventonboarding.link.completed
Channel running eventnumber.connected
Number quality eventnumber.quality_changed
Health state: available, limited, blockedconnection.status and connection.reasons in GET /v1/numbers/{id}, and GET /v1/numbers/{id}/health. See Account health.
List, create and delete templatesGET /v1/templates?wabaId=, POST /v1/templates and DELETE /v1/templates/{id}. See Templates.
Replicate a template to another customerThere is none. Create the template in each WABA with POST /v1/templates. GET /v1/templates/{id} returns the content and the wabaId, which helps copy by hand.
Client balanceGET /v1/usage?numberId=, for display only. There is no balance or top-up.
Channel limitGET /v1/subscription: capacity and capacityLeft. See Plan and numbers.
Channel cancellation requestDELETE /v1/numbers/{id}, which triggers number.disconnected. It does not deregister the number at Meta.

If you come from Gupshup

GupshupLuna
Create an app per customerThere is no app: the instance is the number. Create a connect link with POST /v1/onboarding/links.
Signed embed linkThe connect link: a url with a token, valid for 72 hours.
Callback subscriptions per appPOST /v1/webhooks/endpoints.
Templates per app/v1/templates, per WABA.
Wallet and balanceIt does not exist, by design: each business pays Meta directly. GET /v1/usage only shows usage.
Daily usage per appGET /v1/usage, per number.
Business profile and display nameGET and PATCH /v1/numbers/{id}/profile, without the display name. The business sees and requests that name in Meta’s WhatsApp Manager. See Business profile.

What changes in the webhook#

  • Signature. Each delivery carries X-Luna-Signature: t=...,v1=..., the HMAC-SHA256 of t + . + raw body. See Verify the signature.
  • Order and repeats. Order holds within a conversation, and a delivery may repeat. Deduplicate by the stable event_id.
  • Which account and which customer. Connection and template events carry the waba_id, and every event carries the number object with your customer’s external_id. You do not need to cross lists to know whose event it is.
  • Abandoned link. A customer who closes Meta’s window leaves the link open, with lastFailure and reason: "abandoned". The onboarding.link.failed event arrives later.

Moving a number that is already at the other partner#

  1. The business must own the WhatsApp Business account and have the number released at the previous partner. The prerequisites and the two-step verification PIN are in A number coming from another provider.
  2. Send the connect link (POST /v1/onboarding/links). If the number goes to PIN_REQUIRED, give the PIN in POST /v1/numbers/{id}/pin. A wrong PIN spends one of the registration attempts Meta grants.
  3. Wait for the number.connected event and check connection.canSend in GET /v1/numbers/{id}. Only then switch the number off at the previous partner, so you are not left without a channel in the gap.
  4. Switch your system’s webhook: the events and the signature are different, as in the table above.

Capacity and links#

Luna’s plan defines how many numbers you keep active. The connect link does not reserve a slot: if you send more links than there are slots, the last customers are left with the number "connecting" until a slot is free. Before handing over each link, check the slots, as Plan and numbers explains.