In short
- Message people who wrote to you first, or who asked to hear from you.
- One request sends one message to one conversation. There is no bulk or broadcast sending.
- No spam, scams, phishing, malware, harassment, or illegal or adult content.
- Don't harvest numbers, scrape groups or check lists of numbers.
- Don't work around quotas, rate limits or send caps. We warn, block sends, suspend or close organizations that break these rules.
This summary helps you find your way; the full text below is what applies.
Do
Answer people who wrote to you, or who asked to hear from you.
Don't
Send the same promotion to people who never wrote to you. There is no broadcast feature, and WhatsApp bans numbers that do this.
1Scope
This policy applies to every organization that uses relay and to anyone acting through its account, its numbers or its API keys. It covers the web inbox, the REST API and webhooks, and forms part of the Terms of Use.
You are responsible for how your numbers are used through relay, including by your own software and by anyone you give access to.
2Message people who expect it
Contact a person only when:
- they started the conversation with your number; or
- they gave you their number and agreed to hear from you on WhatsApp, and you can show it.
In every case:
- say who you are in your first message;
- stop when someone asks you to, and don't contact them again from another number;
- never use numbers you bought, rented, scraped or got from someone else.
3No bulk or broadcast sending
relay has no broadcast feature, by design: one request sends one message to one conversation. Sends are paced with random delays, a new number starts with a daily send cap that rises over its first two weeks, and each number can message only a limited number of people who never wrote to it each day.
Do not:
- send the same or a near-identical message to many people who did not write to you;
- loop over a contact list in your own code to rebuild a broadcast;
- spread a campaign across several numbers, organizations or API keys to stay under the caps;
- create groups, or add people to groups, to reach people who haven't agreed to hear from you.
4Follow WhatsApp's rules
relay links numbers the way WhatsApp Web does. It is not an official WhatsApp product, and relay is not affiliated with WhatsApp or Meta.
Follow WhatsApp's own terms and policies for every number you connect. WhatsApp can restrict or ban a number it considers spam, and we can't reverse it.
5Prohibited content
Never use relay to send, store or share:
- spam or unsolicited advertising;
- scams, fraud or phishing, including messages that pretend to come from someone else;
- malware, or links to it;
- harassment, threats, hate speech or incitement to violence;
- sexual or adult content, and anything that sexualises minors;
- content that is illegal where you or the recipient are, or that infringes someone else's rights;
- [CONTENT RULES]
6No scraping or harvesting
Use what your numbers receive only for the conversations it belongs to. Do not:
- collect phone numbers, names or profile details to build lists, sell them, or contact people outside their conversation;
- extract group members to message them one by one;
- join groups only to collect their participants.
7No automated checking of number lists
The number-check endpoint, POST /v1/contacts/check, answers for one phone per request. Use it only for a person you have a reason to contact, such as a customer who gave you their number.
Do not check lists or ranges of numbers, or call the endpoint in a loop to find out who is on WhatsApp.
8Respect limits and controls
Quotas, rate limits and send caps protect your numbers and the service. Don't work around them: no extra organizations or keys to multiply quotas, no rotating numbers to escape a cap or a ban, no attempt to get past a send block.
| Plan | API requests per minute | API calls per month | Sends per month |
|---|---|---|---|
| Starter | 60 | 10,000 | 10,000 |
| Growth | 300 | 100,000 | 60,000 |
| Business | 1,200 | 1,000,000 | 300,000 |
Swipe sideways to see every column.
Every API key also has a burst cap of 20 requests per second.
9Reselling
Do not resell, sublicense or offer relay to others as your own service without a written agreement with us [RESELLER TERMS].
10Security testing
Test the security of relay only under the disclosure policy on our Security page. Never try to reach another organization's data, disrupt the service or load-test it.
11Enforcement
When we see a breach of this policy, we act in proportion to the harm, usually one step at a time:
11.1Warning
We write to the organization owner with what we saw and what has to stop.
11.2Send block
We turn on the organization's kill switch: every send, from the inbox and the API, is refused until we lift it. Your chats stay readable.
11.3Suspension
We suspend access to the organization while the issue is resolved, as the Terms provide.
11.4Termination
We close the organization under the Terms. Its data is deleted as described in the Data Processing Agreement.
We may skip steps when the use is clearly illegal, harms people, or puts the service or other customers' numbers at risk. If you think we got it wrong, reply to our notice.
12Report abuse
If a number connected to relay sent you spam, a scam or abuse, write to support@wrelay.site with the number that wrote to you, the date and time, and what was sent.
We use your report only to investigate and act on it, and we reply within [ABUSE RESPONSE TIME]. You can also block and report the number directly in WhatsApp.
13Changes to this policy
We may update this policy as the service and the risks change. We announce material changes [NOTICE PERIOD] in advance, and each version carries its effective date.
14Contact
Not sure whether something you plan to build is allowed? Ask us first.
- Report abuse
- support@wrelay.site
- Support
- support@wrelay.site
- Company
- [COMPANY LEGAL NAME], [REGISTERED ADDRESS]