SpamWatch
1.3K subscribers
4 photos
5 links
Antispam service for Telegram.

Think your ban is wrong ? Ask in support.spamwat.ch

spamwat.ch
t.me/tgdrbot?start=spamwatch
Download Telegram
SpamWatch API
To use the API, you can now get an API token here. This token is required to access the API and is used to rate-limit specific requests.

To add the API to your bot, you can use one of the official libraries for Python, NodeJS, Crystal and C# or implement it yourself using the documentation at docs.spamwat.ch

When adding the API to a userbot, please avoid mentioning the group admins for banned users since that gets annoying quick. Instead, don't do anything if you are not admin in the group.

In case you notice any issues with the API or have some questions join support.spamwat.ch
The API and Token Bot should both work again after a small (unplanned) downtime.
Quick reminder that @SpamWatchSupport is the only support group for SpamWatch. Any other group claiming to be SpamWatch Support is fraudulent.
Should Admins of spam adding Chats be banned too or just the Group Owner?
Final Results
56%
Yes they should be banned.
36%
No. Just the owner.
8%
Answer for bots.
Fake Rose Federation
Since there have been some fake SpamWatch Federations in Rose please run /chatfed in your group and double check these:
- FedID is 1c2221d9-aa27-4baf-b77c-8822b36254d2
- Owner is @SitiSchu (172811422)
- Number of admins is 1

If any of these don't match up run /leavefed and then /joinfed 1c2221d9-aa27-4baf-b77c-8822b36254d2 to join the real SpamWatch Federation.
Bot Downtime
@SpamWatchBot will be down for maintenance for ~30 minutes
Bot Downtime
@SpamWatchBot is back up again and running open source code now: SpamWatchBot
API Failing
Hetzner is currently having issues with their nodes and one of the affected Nodes happens to be the database server for the SpamWatch API.
Check Hetzner's Status Page for updates.
API Up
Issue should be resolved.
API Down
Hetzner is having issues again so the API is still unavailable.
API Up
Issue has been resolved.
Server Upgrade
The server running the API will be upgraded from Debian 9 to Debian 12 so in case any issues arise, this might be why.