Neike

Neike sits between Meta and your system. It verifies every inbound signature, normalises WhatsApp, Instagram and Messenger into a single message format, queues delivery with retries, and meters usage. You expose one URL and call one API.

One format, three channels

The same conversation + message envelope whether the customer wrote on WhatsApp, Instagram Direct or Messenger. Your handler does not branch per platform.

Delivery you can trust

Inbound and outbound both run through queues with retries and an event store. A failed dispatch can be replayed instead of disappearing.

Onboarding you can embed

Drop Neike’s signup into an iframe inside your own product. Meta validates one origin — ours — and every one of your customers reuses it.

Signed both ways

We verify Meta’s HMAC signature before touching a payload, and every dispatch to you carries the shared token you configured.

Ads and conversations, together

Connect Meta ad accounts, publish campaigns and read results through the same API — and every Click-to-WhatsApp conversation arrives with the ad that started it.

Where to go next

• Quickstart — connect a channel, receive your first message and reply, in the order you would actually do it.
• Core concepts — channels, the message envelope, webhooks and scopes, explained once so the rest of the docs are short.
• Embedded signup — let your own customers connect their WhatsApp number without leaving your product.
• Marketing — connect a Meta ad account, publish an ad and attribute the conversations it brings.