Try your integration without sending to customers.
Test keys use the same endpoints and response shapes as live keys, so your code does not change when you move to live. The only difference is where messages may be sent.
Are messages from a test key really sent?
Yes, but only to the test numbers you register (up to 5). Messages to other numbers are refused with `test_number_required`, so a leaked test key cannot be used to send to customers.
Test key rules
- Sends and replies only to test numbers. Reading contacts, conversations, channels, and templates still works, according to the key's permissions.
- Does not use the plan's message quota. Its own limits: 60 requests per minute and 100 messages per day per business.
- Can be created on every plan, including plans without the API feature.
- Responses carry
"test": trueand the headerKlikflow-Mode: test; the messages are marked as test in the Inbox. - The status of messages sent with a test key reaches webhooks with
test: true. To try other events, use Send test event (Kirim event uji) in Settings › API & Webhook › Webhook (Pengaturan › API & Webhook › Webhook). - The Try it console (Coba) on the reference pages accepts only test keys.
Test numbers
Add them in Settings › API & Webhook › Test numbers (Nomor uji), up to 5 numbers. A number must first have sent a message to one of the business's WhatsApp numbers: send one message from that phone, then add its number. This rule makes sure test numbers belong to people who actually deal with your business.
Templates and costs
WhatsApp Official templates sent with a test key are still really sent to the test number, so their conversation costs, if any, are still recorded in WhatsApp Official › Costs (WhatsApp Official › Biaya). Test templates sparingly.
Moving to live
Create a Live key with the same permissions, channels, and IPs, replace the key on your server, then revoke the test key if it is no longer used. Make sure the Klikflow-Mode header in responses is now live.