Skip to main content

Overview

Joinotify Cloud is a Meta-approved technology provider. We maintain the integration with the Meta Cloud API and expose it to you through our infrastructure — you connect a number, get a token and start sending.

Everything that normally delays an official WhatsApp project falls away:

  • No verified Business Manager. The business verification is ours, not yours.
  • No App Review. You never create or submit an app to Meta.
  • No infrastructure. No webhook to configure on Meta, no System User, no long-lived token to manage.
  • No exposed credentials. Your Joinotify token replaces Meta's; the real credential never leaves our infrastructure.

Two ways to use it​

The API offers two surfaces over the same base. You can mix them in one project, with the same token.

Simplified API​

One sending endpoint, with the payload cut down to what matters: the type goes in the body and the sender number is resolved from your token. It covers text and templates — which are most of any integration’s volume.

POST api.joinotify.com/messages
curl -X POST https://api.joinotify.com/messages \
  -H 'Authorization: Bearer sk_live_xxx' \
  -H 'Content-Type: application/json' \
  -d '{
    "type": "text",
    "to": "5541987111527",
    "body": "Your order #1042 is out for delivery."
  }'

Mirrored API (/v1)​

The Meta Cloud API contract, byte for byte. If you already have code written against the Graph, swap the domain and the token — nothing else changes.

POST api.joinotify.com/v1/{PHONE_NUMBER_ID}/messages
curl -X POST https://api.joinotify.com/v1/106540352242922/messages \
  -H 'Authorization: Bearer sk_live_xxx' \
  -H 'Content-Type: application/json' \
  -d '{
    "messaging_product": "whatsapp",
    "to": "5541987111527",
    "type": "text",
    "text": { "body": "Hello!" }
  }'

See Meta compatibility for the full substitution table and the list of blocked endpoints.

Beyond sending​

The same key reaches what the dashboard does with conversations:

  • Contacts — the contact base, your own fields and marketing consent, to keep your CRM in sync.
  • Flows — trigger an automation built in the editor from your own system.
  • Flows by webhook — your store starts a flow by sending its own data to a URL.
  • Campaigns — one template to a whole audience, with scheduling and automatic pauses.
  • Inbox — the team's conversations, to connect a helpdesk or a bot.

Coexistence with the WhatsApp Business App​

A number connected to Joinotify can keep being used in the WhatsApp Business app on the phone. Conversation history and the contact list can be synced into the Cloud API right after connecting — that's coexistence mode.

Receiving events​

Every incoming message, delivery status update and template change reaches you through a webhook, in the same envelope Meta uses. We sign each delivery with HMAC and retry automatically on failure.

Start with Webhooks.

Next steps​