AHMEDX
Guide

SARWAR ALI MD WhatsApp Bot: Features, Session ID, Pairing Code and Deployment Guide

SARWAR ALI MD, also called SARWAR MD, is a third party WhatsApp Multi Device bot project created and maintained by Sarwar and published in the open at github.com/ayanali7860/SARWAR-ALI-MD. Its README is a short badge page: it names four headline features, carries a GET PAIR button and Heroku and VPS deploy buttons, and prints a reminder that misuse brings a ban risk. The working detail of the project lives in its files, above all config.js, whose settings define most of what the bot does. This guide is checked against the repository itself: its README, config.js, package.json, app.json, LICENSE file and repository tree, together with the pairing addresses the project publishes. Of those addresses, the pairing site named in the repository homepage loads today and works the way the project describes, while the pair button inside the README points at a service that returns a 404 error.

By AHMED X · November 12, 2026 · Last verified November 12, 2026

About

What Is SARWAR ALI MD WhatsApp Bot?

What the project is, who maintains it, where its code lives, and how its short badge style README divides the real detail into its configuration files.

SARWAR ALI MD, also presented as SARWAR MD, is a third party WhatsApp Multi Device bot created and maintained by Sarwar. Its README header describes it, in the project own words, as a multi device WhatsApp bot created and maintained by Sarwar, and its package file names the application SARWAR-MD with index.js as its main file and a start script that runs the bot under PM2. The package file lists the WhiskeySockets Baileys package among its dependencies.

The project lives in one public repository, ayanali7860/SARWAR-ALI-MD, which is not a fork and which the GitHub API reports under the Apache License 2.0. The repository tree is compact: README.md, config.js, command.js, index.js and package.json, together with deployment files named app.json, a Procfile, a Dockerfile, heroku.yml, koyeb.yaml and railway.toml, and a LICENSE file. The README itself is a badge page with four short sections: Fork and Star, Get Pair, Deploy Now and a features list, followed by a reminder and a disclaimer. Almost everything a user can change about the bot sits in config.js rather than in the README.

On licensing, the records agree. The LICENSE file in the repository carries the Apache License 2.0 text, and the GitHub API detects Apache-2.0 for the repository, so this guide names the Apache License 2.0 for SARWAR ALI MD.

Features

SARWAR ALI MD WhatsApp Bot Features

The README names four headline features and nothing more. Everything beyond those four comes from the settings its config.js carries, and the cards below keep the two sources separate so a reader can tell a documented feature from a configuration switch.

Media Downloading

The first headline feature in the README list, written there as MEDIA DOWNLOAD. The README names no supported platforms and no download commands, so this guide publishes none: anyone quoting a platform list for SARWAR MD is going beyond what the project documents in its README.

Group Features

The second README headline. The group behaviour behind it sits in config.js: WELCOME for welcome and goodbye messages, ANTI_LINK for link protection, ADMIN_EVENTS for knowing who promoted or dismissed a member, and ANTI_BAD for bad word protection. Each setting can be switched on or off.

Automatic Replies

The third README headline, AUTO REPLY, matches the AUTO_REPLY setting in config.js. Beside it the same file carries MENTION_REPLY, an automatic voice reply when someone mentions the bot, and AUTO_VOICE for automatic voice replies.

Automatic Recording and Hyping

The fourth README headline, written there as AUTO RECORDING / HYPING. config.js carries the matching AUTO_RECORDING setting, which controls the automatic recording presence the bot shows.

Status Automation

Not a README headline, but a full family inside config.js: AUTO_STATUS_SEEN for automatically marking statuses as seen, AUTO_STATUS_REPLY for automatic replies to statuses, AUTO_STATUS_REACT for automatic reactions to statuses, and AUTO_STATUS_MSG for the text of the automatic status reply.

Anti Delete

config.js carries ANTI_DELETE together with ANTI_DEL_PATH, which chooses where a deleted message is resent: the shipped value sends it to the inbox, and the file comment explains that the same chat is the other choice.

Message Reading and Reactions

READ_MESSAGE controls automatic message reading and READ_CMD marks commands as read. AUTO_REACT switches automatic reactions, and CUSTOM_REACT together with CUSTOM_REACT_EMOJIS lets the owner define a custom reaction set.

Anti View Once and Anti Call

ANTI_VV in config.js controls the anti view once behaviour, and ANTI_CALL controls automatic rejection of incoming WhatsApp calls. Both are plain configuration switches in the file, documented there with one line comments.

Session ID

How to Get a SARWAR ALI MD Session ID

The project publishes two different pairing routes, and they do not lead to the same place today. The README GET PAIR button points at a Railway hosted service that returns a 404 error, while the repository homepage names a pairing site that loads and shows exactly the server selection flow the project describes. This section records both and walks through the working one.

01

Start From the Repository

Open ayanali7860/SARWAR-ALI-MD. Two pairing pointers exist: the GET PAIR button inside the README, and the website address in the repository homepage field. They are different services, and their present day states are different, as the next steps record.

02

The README Pair Button: 404 Today

The README button points to sarwar-md-pair-production-761e.up.railway.app. That address was opened again for this guide and returns a 404 error, so the pairing route printed inside the README does not work today. Nothing in this guide presents it as a working service.

03

The Pairing Site in the Repository Homepage

The repository homepage names sarwar-md-bot.vercel.app, titled SARWAR-MD Pair System. It loads today and presents a Generate Your Pairing Code page with a Select Server control, an Active figure and a connection limit for the chosen server, and a WhatsApp number field. This is the pairing route that matches the flow the project describes.

04

Select a Server

On the pairing site, choose a server from the Select Server list. The page shows the activity and connection limit of the server you pick, so choose one that is shown as available before going further.

05

Enter Your WhatsApp Number

Type your WhatsApp number into the number field. The page itself instructs users to include the country code, giving 92 for Pakistan as its example. Leave out spaces and symbols.

06

Generate the Pairing Code

Use the page option to generate your pairing code. The site creates the code for the number you entered on the server you selected. Pairing codes are temporary, so move to the next step promptly.

07

Enter the Code in WhatsApp

On Android, open WhatsApp, tap the three dot menu, select Linked Devices, tap Link a Device, and choose Link with phone number instead. On iPhone, open WhatsApp, go to Settings, then Linked Devices, then Link a Device, and choose the phone number option. Enter the generated code and wait for WhatsApp to complete the linking.

08

Save the Session ID and Keep It Private

After linking, follow the pairing site instructions to obtain your Session ID: the authentication value the bot consumes through the SESSION_ID setting in config.js and app.json. Treat it as a credential. Anyone holding working session credentials may be able to access the WhatsApp session they came from, so never post it in a chat, a screenshot or a public fork.

Deployment

How to Deploy SARWAR ALI MD WhatsApp Bot

The README Deploy Now section carries exactly two buttons, Heroku and VPS, and this guide presents deployment at the level those buttons and the repository files support. The repository also contains deployment files for other environments; they are recorded as files that exist, not as documented procedures.

01

Fork the Repository First

The README opens with a Fork and Star section asking users to fork and star the repository before using it. Work from your own fork so the settings and session you configure belong to your copy.

02

Heroku: The README Template Button

The Deploy Now Heroku button points to the Heroku dashboard template address for this repository, dashboard.heroku.com/new with the repository as its template. That is the documented Heroku route, and its destination is fixed by the README link itself.

03

Heroku: The Settings the Template Asks For

The repository app.json defines what the template collects: SESSION_ID is required and described as the place to put the session id, AUTO_STATUS_SEEN, AUTO_STATUS_REPLY, AUTO_STATUS_REACT, AUTO_STATUS_MSG and ANTI_LINK are also marked required, and a long optional list follows, from PREFIX and MODE to OWNER_NAME and OWNER_NUMBER. app.json uses the heroku-24 stack with the Node.js buildpack. Replace every shipped value with your own before deploying.

04

VPS: The README VPS Button

The second Deploy Now button points to sarwar-md-vps.vercel.app, a VPS deployment page for the project. That page loads today. A VPS route gives you control of the server environment, and the repository files define what the bot needs there, as the next steps record.

05

VPS: What the Package File Requires

The package file engines field asks for Node.js at version 24.x or newer and npm at version 10.x or newer. On your server, clone your fork, run npm install to install the dependencies the package file declares, and create the environment configuration with your own SESSION_ID value.

06

VPS: The Start Script

The package file start script runs the application under PM2: it starts index.js with the process name SARWAR-MD and attaches to it, and stop and restart scripts for the same PM2 process sit beside it. After starting, read the terminal output and confirm the WhatsApp connection is established.

07

Deployment Files That Exist Without a Documented Procedure

The repository tree also contains a Dockerfile, koyeb.yaml, railway.toml, heroku.yml and a Procfile. Their presence is file evidence that container and platform shapes were prepared, but the README documents no procedure for them, so this guide publishes none.

Configuration

SARWAR ALI MD Configuration Settings

The settings below are read from the real config.js in the repository, which loads its values from the environment or a config.env file. Only settings that exist in that file are listed, and every shipped default belongs to the project side and must be replaced with your own values.

SESSION_ID

The authentication value the whole setup depends on, read from the environment at the top of config.js and also required by app.json for the Heroku template. Generate it through the pairing route and keep it private.

PREFIX

The command prefix, shipped in config.js with a dot as its value. The app.json description adds a warning in the project own words: do not apply a null prefix. Individual command names are not published in the README; the repository carries a command.js file for command handling, and this guide invents no command list.

BOT_NAME, OWNER_NAME, OWNER_NUMBER and DESCRIPTION

The identity settings: bot name, owner name, owner number and the description shown with the menu, together with MENU_IMAGE_URL, ALIVE_IMG, LIVE_MSG and STICKER_NAME for the menu image, alive message and sticker pack name. config.js ships these with project side values, including an owner number written into the file; replace all of them with your own before any run.

MODE and PUBLIC_MODE

MODE chooses how the bot works, and the config.js comment gives its four values: public, private, inbox and group. A separate PUBLIC_MODE setting sits beside it in the same file.

Status Settings

AUTO_STATUS_SEEN, AUTO_STATUS_REPLY and AUTO_STATUS_REACT control automatic status viewing, replies and reactions, and AUTO_STATUS_MSG holds the text used for the automatic status reply.

Protection Settings

ANTI_DELETE with ANTI_DEL_PATH for deleted message handling, ANTI_LINK and DELETE_LINKS for group link control, ANTI_BAD for bad words, ANTI_VV for view once media, and ANTI_CALL for automatic call rejection.

Behaviour Settings

AUTO_REPLY, AUTO_VOICE and MENTION_REPLY for automatic replies, AUTO_RECORDING and AUTO_TYPING for presence, ALWAYS_ONLINE for the online state, READ_MESSAGE and READ_CMD for message reading, AUTO_STICKER for automatic stickers, and WELCOME and ADMIN_EVENTS for group join, leave and administrator events.

Official Links

SARWAR ALI MD Official Links

The resources checked for this guide: the repository and its README, the pairing site that loads today, the pairing and deployment addresses that do not, the project channel its README links, and the library the bot is built on.

Safety

Is SARWAR ALI MD WhatsApp Bot Safe?

The warning the project prints about itself, the precautions that apply to its pairing routes and shipped configuration values, and its licensing position.

SARWAR ALI MD is an unofficial third party bot, and its README prints a reminder in plain terms: the bot is not affiliated with WhatsApp Inc, misuse brings a ban risk, users should use it responsibly, and the owner is not responsible. Take that reminder at face value. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and no setting in any bot can promise protection from that. Use a separate number for testing rather than your main personal or business number, and avoid spam and abusive automation of any kind.

Be careful about which pairing address you trust. The pairing site named in the repository homepage loads and works as documented, but the pair button inside the README itself points at a service that returns a 404 error today. A dead official route is exactly what fake session websites exploit, so only type your number into a pairing page you can trace back to the repository, and treat every other SARWAR MD session page as unverified. Never share your Session ID, and never upload it to a public repository.

Check the shipped configuration before you run anything. config.js arrives with project side default values, including an owner number and a developer number written into the file, and those values must be replaced with your own. The repository is open, so read its JavaScript files and dependencies before running them. On licensing, the LICENSE file carries the Apache License 2.0 text and the GitHub API detects Apache-2.0 for the repository, and the README disclaimer adds the creator own instruction not to sell or misuse the project.

Alternatives

Free MD Bots You Can Deploy on AHMED X

Want more free MD bots like this? These bots on AHMED X cover the same ground: free deploy, pair-code setup, group and chat automation.

ASTRA X

ASTRA X

WhatsApp MD Bot

Advanced AI-first MD bot with dual AI engines, media downloaders and deep group management.

Geston-MD

Geston-MD

WhatsApp MD Bot

Lightning-fast Baileys multi-device bot with AI chat, group protection and replies in many languages.

CELESTIA

CELESTIA

WhatsApp MD Bot

A polished multi-device WhatsApp bot with a large command library, AI chat and safe group tools.

TOXIC-MD

TOXIC-MD

WhatsApp MD Bot

Lightning-fast WhatsApp bot built on Baileys, made for speed and everyday automation.

SUKUNA-MD

SUKUNA-MD

WhatsApp MD Bot

A modular WhatsApp MD bot with group administration, media tools, protection engines and AI voice replies.

Levanter

Levanter

WhatsApp MD Bot

Multi-device WhatsApp bot packed with group protection, AI chat and a plugin system.

View all bots in the catalog

FAQ

SARWAR ALI MD FAQs

Short answers to the questions readers ask most about SARWAR ALI MD.

SARWAR ALI MD, also called SARWAR MD, is a third party WhatsApp Multi Device bot project created and maintained by Sarwar and published at github.com/ayanali7860/SARWAR-ALI-MD. Its README names media downloading, group features, automatic replies and automatic recording as its headline features, and most of its behaviour is controlled through the settings in config.js.

Use the pairing site named in the repository homepage, sarwar-md-bot.vercel.app: select a server, enter your WhatsApp number with its country code, generate the pairing code, and enter it under Linked Devices in WhatsApp. Note that the GET PAIR button inside the README points to a different service that returns a 404 error today.

Yes. Pairing code linking is the route its pairing site is built around: pick a server, enter the number, generate the code, and complete the link with the phone number option in WhatsApp Linked Devices.

The README documents two: Heroku, through the template button in its Deploy Now section with the settings its app.json defines, and a VPS, through the VPS page its second button opens. The repository tree also contains a Dockerfile, koyeb.yaml, railway.toml, heroku.yml and a Procfile as files, without a documented procedure for them in the README.

A dot. config.js ships PREFIX with a dot as its value, and app.json repeats the same default with a warning not to apply a null prefix. You can change it through the PREFIX setting.

No. The README publishes no command names or categories, so this guide publishes none. The repository carries a command.js file for command handling, and any command list for this bot found elsewhere does not come from the project README this guide could check.

The Apache License 2.0. The LICENSE file in the repository carries the Apache License 2.0 text and the GitHub API detects Apache-2.0 for the repository, so the records agree.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the SARWAR ALI MD repository as it could be opened on the last verified date: ayanali7860/SARWAR-ALI-MD, read through the GitHub API and its raw files, including its README with the real destinations behind its pair and deploy buttons, its config.js read in full, its package.json, its app.json, its LICENSE file and its repository tree. The pairing site named in the repository homepage was opened and shows the server selection flow described in this guide, and the VPS deployment page behind the README button loads. The pair service behind the README GET PAIR button returns a 404 error. Where the README publishes nothing, this guide says so instead of filling the gap: the README names no media platforms and no commands, so none are published here.

AHMED X provides this article for educational and informational purposes only. AHMED X is not the developer or owner of SARWAR ALI MD and does not claim any partnership or official affiliation with Sarwar or the project contributors.

AHMED X is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta. WhatsApp is a trademark of its respective owner. Use unofficial WhatsApp automation at your own risk.

Keep Reading

Related WhatsApp Bot Guides

More free WhatsApp bot guides from the AHMED X blog.

Guide

SIGMA MD WhatsApp Bot: Features, Session ID and Deployment Guide

SIGMA MD is a third party WhatsApp Multi Device bot project developed by Maher Zubair. The first fact a reader needs is where the code can still be read: the original repository, Maher-Zubair/SIGMA-MD, returns a 404 error on the web today, and the GitHub API reports that repository as access blocked. The full record survives in a public copy under the NeutronDroid account, an independent re-upload rather than a GitHub fork, whose package file reads version 1.4.9 and whose README and changelog match the last release the changelog records. A documentation mirror on GitLab also loads today. This guide is checked against the surviving copy: its README with its feature list and changelog, its app.json, its Setting.js, its sample configuration and its LICENSE file. One more present day fact shapes everything about using this bot: the developer domain the README sends readers to for a Session ID and for every deploy helper page, maher-zubair.tech, does not respond at all today.

Read the guide
Guide

SILVA MD WhatsApp Bot: Features, Session ID and Deployment Guide

SILVA MD is a third party WhatsApp Multi Device bot project from Silva Tech Inc, published in the open at github.com/SilvaTechB/silva-md-bot and actively maintained. Its README documents an AI assistant called Agent v2 backed by the ch.at service, a protection suite covering calls, deleted messages, links, view once media and group abuse, media downloaders, group management, games and a set of character themes. The repository homepage names its session selector site, which loads today and is where the README session flow begins, and the README recommends the project own Silva Host platform for deployment. This guide is checked against the repository itself: its README, package.json, LICENSE file and repository tree, together with the session and hosting addresses the README prints. Of those addresses, one documented route has broken since the README was written: the fork checker page the Heroku method depends on returns a 404 error today, and the TalkDrove sharing page did not load when checked.

Read the guide
Guide

What Is SUBZERO MD WhatsApp Bot?

SUBZERO MD is a third party WhatsApp Multi Device bot project by Darrell Mucheri, known online as Mr Frank, built with JavaScript and presented by its README as version 7. Its GitHub repository is live and links a working session service that offers both pair code and QR code login. One caution runs through this guide: the README itself publishes no feature catalogue and no command list, so the feature descriptions in circulation come from the developer project websites, and this guide keeps those two records separate throughout.

Read the guide
Guide

SUHAIL MD WhatsApp Bot: Features, Session ID and Deployment Guide

SUHAIL MD is an older third party WhatsApp Multi Device bot project from the Suhail Tech Info name, built on the Baileys library and designed around entertainment and interactive games. The plain facts first: the original GitHub repository cannot be opened today, the GitHub API reports its access as blocked, and the project appears no longer maintained, with the developer channel having directed users to a newer project called Suhail X, whose repository is also blocked on GitHub today. Everything in this guide is therefore checked against a publicly accessible copy of the repository, reu12th/Suhail-Md-Railway, which preserves the README and the project files, and this guide covers the original SUHAIL MD only, not SUHAIL MD V2 and not Suhail X.

Read the guide

Deploy Your Own Free WhatsApp Bot Today

Pick a bot from the AHMED X catalog and deploy it free in minutes. No server, no coding.

Browse Free Bots