MyZapz
Built on the WhatsApp Business Platform

The quiet link between your tools and WhatsApp.

MyZapz connects business software to Meta's WhatsApp Cloud API. It relays messages and delivery events, securely, for businesses that use our partners' platforms.

Cloud API
Official Meta integration
Embedded Signup
Businesses connect their own number
PDPA 2010
Malaysian data protection

How the connection works

MyZapz sits between a business's software and Meta. It has no inbox, chatbot or sign-up of its own. It only moves messages and events.

1

The business connects

Inside a partner's software, the business signs in with Facebook through Meta's Embedded Signup and picks its own WhatsApp number.

2

Messages flow both ways

Customer messages arrive as Meta webhooks. MyZapz verifies them and passes them on. Replies go back out through the Cloud API.

3

The business stays in control

The account, number and conversations remain the business's. Removing MyZapz in Meta Business Settings ends access at once.

What passes through MyZapz

Four everyday examples. Each card shows what the customer sees, and the WhatsApp Business Platform event behind it.

Hi, do you deliver to Shah Alam?10:02
messages · inbound

A customer asks a question

Meta sends the message to MyZapz, which forwards it to the business's inbox.

Hi, do you deliver to Shah Alam?10:02
Yes, free delivery above RM50.10:04
messages · send

Staff reply in their tool

The reply goes out through the Cloud API within the 24-hour service window.

Sent10:04:01
Delivered10:04:02
Read10:04:37
messages · statuses

Delivery is reported back

Sent, delivered and read events show the business whether its message arrived.

Hi Aisyah, your appointment is on Sat, 1 Nov at 10:00 am. Reply here to change it.Fri 18:00Reschedule
template · opted-in

An approved reminder

Meta-approved templates go only to customers who agreed to receive them.

Under the hood

Every webhook from Meta is checked against its signature before MyZapz forwards it. Access tokens are stored encrypted and never logged.

// POST /webhooks/whatsapp  from Meta
{
  "field": "messages",
  "value": {
    "messages": [{
      "from": "60123456789",
      "type": "text",
      "text": { "body": "Hi, do you deliver to Shah Alam?" }
    }]
  }
}

Permissions we ask for, and why

A business grants these during Embedded Signup. Each is used for one purpose only.

Permission
Used for
Never used for
whatsapp_business_messaging
Sending the business's replies and approved templates; receiving messages and delivery statuses.
Messaging anyone who has not contacted the business or opted in.
whatsapp_business_management
Reading phone numbers and templates, submitting templates for review, subscribing to webhooks.
Changing account settings the business did not ask to change.
business_management
Identifying which Business Portfolio owns the connected WhatsApp Business Account.
Reading or managing ad accounts, Pages or other assets.
Webhook fields messages message_template_status_update phone_number_quality_update account_update

Encrypted throughout

TLS in transit, encryption at rest, signed webhooks.

Business-owned data

Numbers, templates and chats belong to the business.

Deleted on request

Data removed within 30 days of a request or disconnect.

Meta policies enforced

Opt-in only, under WhatsApp's Business and Commerce policies.