Question 1

How do I connect my first number?

Accepted Answer

Create an account, open a session, and scan the QR in WhatsApp under Linked Devices, or use a pairing code. Then call the API with your key. Minutes, not days: there is no approval flow to wait on.

Question 2

Do I need my own WhatsApp Business account?

Accepted Answer

No. You link a normal WhatsApp number, personal or Business app, the same way WhatsApp Web links a device.

Question 3

Can I use my existing WhatsApp number, or do I need to migrate?

Accepted Answer

Use your existing number. There is no migration. Link it by QR or pairing code, and change the linked number later at no extra cost.

Question 4

Can I integrate with Make, n8n, or Zapier?

Accepted Answer

Yes, via native and community nodes, or plain HTTP requests and webhooks. No custom backend required.

Question 5

How many numbers can I connect?

Accepted Answer

One number per session. For several numbers, run several sessions. Your plan sets how many at once: 1 on Solo up to 20 on Scale, and Starter, Growth and Scale sell extra numbers as an add-on up to their ceilings (9, 19 and 79). Past that, Reseller terms start at 80+ numbers.

Question 6

Is there a free trial?

Accepted Answer

Yes. A free developer sandbox for 3 days, no card. Pair a real number and send up to 1,000 real messages against the full API, with heavier throttling. Pick a plan when you are ready to ship.

Question 7

Do I need WhatsApp approval or message templates?

Accepted Answer

No. There is no template moderation and no approval flow. Link your number to a session and you can send and receive immediately.

Question 8

Can I keep using WhatsApp on my phone after connecting?

Accepted Answer

Yes. The API drives a linked-device session, so your phone and WhatsApp Web keep working in parallel. Using the phone occasionally keeps the session healthy; rarely, WhatsApp resets a linked session and asks you to re-pair.

Question 9

What if a WALayer server restarts?

Accepted Answer

Nothing changes for you. Sessions recover on other capacity in under 90 seconds, without re-pairing.

Question 10

Can two of my team touch one session at once?

Accepted Answer

The platform guarantees exactly one process ever owns a session's connection. That is what prevents the credential corruption that forces a QR re-scan.

Question 11

Do you use dedicated proxies per number?

Accepted Answer

No. Sessions send over the platform's own network, which is why per-number pacing and warmup are enforced so carefully: sending reputation is shared, so one number behaving like a bulk sender is everyone's problem. Rate ceilings are applied server-side by throttling, never by cutting a send off mid-flight, and every throttle event is logged and visible.

Question 12

Will recipients know I am using WALayer?

Accepted Answer

No. Messages come from your own number, natively. There is no WALayer branding on anything your customers see.

Question 13

Can WALayer stop my number getting banned?

Accepted Answer

No one can. Bans are WhatsApp's decision, driven mostly by behaviour. We reduce the risk as far as it can be reduced with automatic warmup and human-like pacing, and if it happens we detect it, freeze sends, and help you recover onto a fresh number.

Question 14

What happens if my number gets banned?

Accepted Answer

We detect it, freeze sends, let you export any queued messages, and walk you through recovery onto a fresh number, rather than failing silently.

Question 15

What happens if I log out of WhatsApp on my phone?

Accepted Answer

Your session disconnects and we tell you immediately, in the dashboard and by webhook. Re-linking takes seconds.

Question 16

What message types can I send?

Accepted Answer

All 22: text, image, video, audio/voice, document, sticker, location, contact, reaction, poll, reply, forward, revoke, edit, presence, short video (PTV), GIF, link preview, live location, contact list, and stories. Interactive buttons and lists are engine-flagged where WhatsApp permits them.

Question 17

Can I receive messages too?

Accepted Answer

Yes. Every inbound message, receipt, and status change arrives as a signed webhook in real time, so your own systems see it the moment it happens.

Question 18

How do webhooks stay secure?

Accepted Answer

Each delivery is HMAC-signed over the raw body with a timestamp and delivery id. Verify the signature, enforce a 5-minute replay window, and dedupe on the delivery id.

Question 19

What if my endpoint is down?

Accepted Answer

We retry on a backoff, then dead-letter, and give you event history plus one-click redelivery so nothing is lost.

Question 20

How is this different from the official WhatsApp Business API?

Accepted Answer

The official Cloud API charges per conversation, needs approved templates and business verification, and cannot touch groups or channels. WALayer links your own number for a flat fee with no templates, in exchange for operating unofficially, which we are upfront about. Full comparison on the Developers page.

Question 21

What payment methods do you accept?

Accepted Answer

Cards and common methods, handled by our payment processor. WALayer never sees or stores card details.

Question 22

Can I cancel anytime?

Accepted Answer

Yes. Upgrades take effect immediately; downgrades at the next cycle. See the Refund Policy for details.

Answers, including the uncomfortable ones.

Getting started

Reliability & deliverability

Bans & safety

Messaging & webhooks

Billing

Skip Meta approvals. Skip message fees. Skip the dropped messages.