AHMEDX
Guide

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

XBOT MD, written X BOT MD inside its repository, is a third party WhatsApp Multi Device bot project by Aswin Sparky. The original repository is live today under the renamed Aswin-Sparky account, with the older A-S-W-I-N-S-P-A-R-K-Y address redirecting to it, and this guide is checked against that repository directly: its README documents QR authentication and four deployment routes, and its session service was opened again for this guide and is working, asking visitors to sign in with GitHub and fork the repository before it offers QR pairing and a pair code option. A separate pairing project by the same developer exists only as source code to host yourself, and the README publishes no command list, so this guide publishes none.

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

About

What Is XBOT MD WhatsApp Bot?

What the project is, who developed it, where its repository lives today, and the version presentation its files give it.

XBOT MD, also written X BOT MD, is a third party WhatsApp Multi Device bot project by Aswin Sparky, whose repository description calls it a multifunctional WhatsApp bot project. The original repository is live today, but its address has moved: the developer account was renamed from A-S-W-I-N-S-P-A-R-K-Y to Aswin-Sparky, and the old repository address now redirects to Aswin-Sparky/X--BOT--MD. This guide is checked against the repository at its current address. Several unrelated bots use similar names, including XBOT MD2 projects by other developers, and nothing from those projects is merged into this guide.

On version, the files disagree. The README title presents the project as X BOT MD 3.6.0, while package.json ships a different version value, 3.7.0, with index.js as its main file and the author given as ASWIN SPARKY. This guide reports both values exactly as they stand: 3.6.0 is the version presentation the README gives its readers, and 3.7.0 is the version string the package file carries.

The repository tree holds index.js as the main application, config.js for configuration, a lib folder with database, session and helper modules, a plugins folder, and the deployment and project files package.json, Dockerfile, app.json, heroku.yml and LICENSE. The README credits THEJUS for beta testing and debugging. The package file shows the shape of the application: it runs under PM2 from its start script and depends on a baileys package, Express, Sequelize with Postgres support and a long list of media and utility libraries.

Features

XBOT MD WhatsApp Bot Features

The X BOT MD README is short: it describes a multifunctional bot and documents authentication and deployment, but it publishes no feature list, no command list and no plugin categories. The cards below cover only what the README and the repository files actually establish.

WhatsApp Multi Device Bot

The repository describes the project as a multifunctional WhatsApp bot, and the README is built around linking a WhatsApp account through its session process. Beyond that one line description, the README documents no individual features.

QR Code Authentication

The README SCAN QR section carries two server buttons, and both point at the same address, x-bot-md-qr.koyeb.app. Scanning the QR is presented there as the way to get the Session ID. That service was opened for this guide and its present day state is covered in the session section.

Plugin Structure

The repository tree contains a dedicated plugins folder holding files for areas such as menus, downloading, groups and conversion, beside a pluginsCore folder with language files. The README documents none of these as features and names no plugin categories, so this guide records the structure without inventing a feature list from file names.

Multiple Deployment Options

The README documents four deployment destinations: Panel hosting through its wiki guide, Heroku through a template link, Koyeb through a prefilled deploy link, and Render through dashboard steps. Each is covered in the deployment section.

Configuration Support

The tree carries config.js, and that file reads a long list of environment settings covering the session, the database, platform API keys and automatic behaviour. The setting names this guide publishes were read from config.js itself and from the Koyeb template in the README.

Docker Configuration

The repository tree contains a Dockerfile, and the Koyeb deploy link in the README selects the Dockerfile builder, which is file evidence that a container route was prepared. The README publishes no Docker tutorial, so this guide presents no Docker procedure for X BOT MD.

Session ID

How to Get an XBOT MD Session ID

The README route is QR authentication through one service linked behind both of its server buttons. That service was opened again for this guide: it loads today and presents itself as the X-BOT-MD session platform, and it asks visitors to sign in with GitHub and hold a fork of the repository before offering QR pairing and a pair code option.

01

Fork the Repository First

The README first instruction is blunt: you must fork the repository before deployment, and its session service repeats the requirement. Open the X--BOT--MD repository at its current Aswin-Sparky address and fork it to your own GitHub account before starting authentication.

02

Open the QR Service From the README

The SCAN QR section of the README carries Server 1 and Server 2 buttons. Both point to the same address, x-bot-md-qr.koyeb.app, so there is effectively one documented session service, not two different ones.

03

The Service Today: Live, Behind a GitHub Sign In

That address was opened for this guide and loads as an X-BOT-MD session page. It asks you to sign in with GitHub and to have a fork of the repository, presenting those as its verification step, and then offers two session routes: a QR code pairing option and a pair code option where you enter your phone number. Treat any other X BOT MD session page as unverified, because this is the only service the README links.

04

Scan the QR Code With Linked Devices

Choose the QR option and scan with the phone that holds the number. On Android, open WhatsApp, tap the three dot menu, select Linked Devices, tap Link a Device and scan. On iPhone, open WhatsApp, go to Settings, select Linked Devices, tap Link a Device and scan. Wait for WhatsApp to complete the linking.

05

Or Use the Pair Code Option on the Same Service

The same service also offers a pair code route on its session page: enter your phone number with its country code and use the code it gives you through the link with phone number option inside WhatsApp Linked Devices. This is a feature of the hosted service as it stands today; the original repository README itself documents only the QR route.

06

Keep the Session ID Private

After linking, the service provides the session material the bot needs, and the project consumes it as the SESSION_ID setting. Anyone holding usable authentication credentials may be able to access the WhatsApp session they came from, so never share your Session ID in chats, screenshots or public forks.

Pairing

The Separate X MD Pair Pairing Service

Pairing code support for X BOT MD also exists as a separate repository by the same developer, X-MD-PAIR. It is a self hosted web service, not a public website: its README links no hosted instance, so this guide presents it as source code you run yourself and never as a live pairing page.

01

A Separate Repository, Not Part of the Bot

X-MD-PAIR lives in its own repository under the same renamed Aswin-Sparky account. The main X BOT MD repository does not bundle it, and the pair service README describes it as a web based pairing service for X-BOT-MD that you set up yourself.

02

Eight Character Pairing Codes

Its README documents the model plainly: an eight character pairing code instead of QR scanning, a responsive web interface with a country code selector, and session storage in MongoDB with its own Session IDs.

03

Session ID Delivered by WhatsApp Message

The README feature list states that after successful pairing the server restarts for a clean state and the user receives their Session ID directly through a WhatsApp message. Its MakeSession function then restores the creds.json file the bot needs from that session.

04

You Host It Yourself

The README quick start is a self hosting recipe: Node.js 18 or above, a MongoDB instance, clone the repository, install dependencies, copy the example environment file and fill in your MongoDB value, then run it directly or under PM2 or Docker. No public hosted address for this service is published in its README, and none could be verified for this guide.

Deployment

How to Deploy XBOT MD WhatsApp Bot

The README documents four deployment routes and gives each one a real link: a panel wiki guide, a Heroku template, a prefilled Koyeb deploy link whose fields can be read directly, and Render dashboard steps that name its two prerequisites. The steps below stay at exactly that level.

01

Panel Hosting: The Wiki Guide

The README DEPLOY TO PANEL section says to create a panel account first and then follow its linked guide. That link leads to the deploy vps page of the repository wiki, which was checked for this guide and exists today. The README names no panel provider and no environment list for this route, so follow the wiki page itself rather than any summary of it.

02

Heroku: The Template Link

The README Heroku section first links the Heroku account creation page and then a deploy button carrying the template form of this repository address. The tree supports the route with app.json and heroku.yml. Configure the settings the application asks for at deploy time and check the logs after the build.

03

Koyeb: The Prefilled Deploy Link

The README Koyeb section asks for a Koyeb account and a Koyeb API key, then gives a deploy link with the configuration fields already named: SESSION_ID, WORK_TYPE, HANDLERS, BOT_INFO, SUDO, STICKER_DATA, DATABASE_URL, KOYEB_SERVICE_NAME and KOYEB_API_KEY, with the Dockerfile builder selected. The link ships example values, including an owner number, and every one of them must be replaced with your own before deploying.

04

Render: Database URL and API Key First

The README Render section is explicit about its prerequisites: create the account, get a DATABASE_URL from the Render dashboard, get a Render API key from the account settings, and only then deploy through the new web service page it links. config.js confirms the application reads both a database URL and platform API keys.

05

Run Shape From the Package File

Whichever route you choose, the package file defines how the application runs: its start script launches the app under PM2 with the process name X-BOT-MD and attaches to its output, and a matching stop script sits beside it. That is the run method the project files themselves define once dependencies are installed and the session setting is in place.

Configuration

XBOT MD Configuration Settings

The setting names below were read from config.js itself and cross checked against the field list inside the README Koyeb deploy link. Only names are published here; the shipped example values in those files belong to the project side and must be replaced with your own.

SESSION_ID

The authentication setting config.js reads from the environment. It is the value the QR session flow exists to produce, and it should be present before the application starts and kept private afterwards.

WORK_TYPE and HANDLERS

Two fields the Koyeb template names and config.js reads. WORK_TYPE selects the operating mode of the bot, and HANDLERS is the handler setting the template passes alongside it. Follow the names exactly as the files spell them.

BOT_INFO and STICKER_DATA

Presentation settings the template and config.js share: BOT_INFO carries the bot name, owner name and image the application presents, and STICKER_DATA carries the sticker pack naming. Both ship with project example values that deployers replace.

SUDO

The privileged numbers setting. config.js ships with a default number written into the code, and the Koyeb template ships the same style of example value. That number belongs to the project side: replace it with your own number before running the bot, and never treat a shipped value as yours.

DATABASE_URL

The database connection the application requires, read by config.js and named by both the Koyeb template and the Render steps. config.js also carries a fallback database URL with credentials written into the code itself. Never use shipped credentials: set your own DATABASE_URL, because anyone who reads the public file can read the fallback too.

Platform API Keys

config.js reads KOYEB_API_KEY with KOYEB_SERVICE_NAME, and the same file also reads Render and Heroku API key and app name settings. These keys belong to your own hosting accounts and should never be shared or committed to a public fork.

Official Links

XBOT MD Official Links

The resources checked for this guide: the repository at its current renamed address, the session service and its present day state, the separate pairing project, the panel wiki guide, the developer channel, and the library the project builds on.

X BOT MD GitHub Repository

The original X--BOT--MD repository at its current address under the renamed Aswin-Sparky account. The older A-S-W-I-N-S-P-A-R-K-Y address redirects here. It carries the README, config.js, package.json, LICENSE and the tree this guide verified against.

https://github.com/Aswin-Sparky/X--BOT--MD

X BOT MD README

The README inside the original repository: the fork instruction, the SCAN QR section, the four deployment sections and the THEJUS credit this guide is built from.

https://github.com/Aswin-Sparky/X--BOT--MD/blob/main/README.md

X BOT MD Session Service (Live, GitHub Sign In Required)

The x-bot-md-qr.koyeb.app service behind both README SCAN QR buttons. Checked for this guide, it loads as the X-BOT-MD session platform and asks for a GitHub sign in and a fork of the repository before offering QR pairing and a pair code option.

https://x-bot-md-qr.koyeb.app

X MD Pair Repository (Self Hosted Pairing Service)

The separate Aswin-Sparky/X-MD-PAIR repository: an eight character pairing code web service with MongoDB session storage that you deploy yourself. Its README publishes no hosted instance, and none is linked here as a working pairing website.

https://github.com/Aswin-Sparky/X-MD-PAIR

Panel Deployment Wiki Guide

The deploy vps page of the X BOT MD repository wiki, which the README panel section links as its deployment guide. Checked for this guide and present today.

https://github.com/A-S-W-I-N-S-P-A-R-K-Y/X--BOT--MD/wiki/deploy%E2%80%90vps

Developer WhatsApp Channel

The WhatsApp channel the README links under its join for updates heading, presented there as the place to follow the project.

https://whatsapp.com/channel/0029Va9ZOf36rsR1Ym7O2x00

Developer GitHub Profile

The Aswin-Sparky account, renamed from A-S-W-I-N-S-P-A-R-K-Y, which publishes both the X BOT MD repository and the X MD Pair service.

https://github.com/Aswin-Sparky

Baileys Library

The current home of the Baileys library under the WhiskeySockets name. The X BOT MD package file lists a baileys dependency, and the X MD Pair project builds on the WhiskeySockets Baileys package directly.

https://github.com/WhiskeySockets/Baileys

Safety

Is XBOT MD WhatsApp Bot Safe?

The precautions that apply to X BOT MD, including the shipped credentials sitting inside its public configuration file and the disagreement inside its license records.

XBOT MD is an unofficial third party bot. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and no feature 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. Before you authenticate anywhere, check that the page in front of you is the session service the README actually links, because the bot name is shared by unrelated projects and copied session pages are a known trap in this space.

Check the shipped files before you run anything, because this repository needs it more than most. config.js carries a fallback database URL with working style credentials written into the code, and it ships a default owner number as its SUDO value; the Koyeb template in the README ships example values of the same kind. All of those values belong to the project side and are readable by anyone who opens the public repository. Replace every one of them with your own settings, use your own database, and never run the bot against credentials or numbers you found inside its files. Keep your own Session ID and hosting API keys out of chats, screenshots and public forks.

On licensing, the records inside the repository disagree with each other. The LICENSE file in the tree carries the full GNU General Public License version 3 text, and the GitHub API detects GPL-3.0 for the repository. The license field of package.json, however, reads ISC. This guide reports both signals exactly as they stand and names no single license for X BOT MD, so readers should weigh the LICENSE file and the package field together before reusing the code. The separate X MD Pair repository is cleaner: its own LICENSE file carries the MIT License text with a copyright line for Aswin Sparky.

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

XBOT MD FAQs

Short answers to the questions readers ask most about XBOT MD.

XBOT MD, written X BOT MD in its repository, is a third party WhatsApp Multi Device bot project by Aswin Sparky. Its repository description calls it a multifunctional WhatsApp bot project, and its README documents QR authentication and deployment on Panel hosting, Heroku, Koyeb and Render. The README publishes no command list.

Aswin Sparky. The package file gives its author as ASWIN SPARKY, the repository lives under his renamed Aswin-Sparky account, and the README credits THEJUS for beta testing and debugging.

The README title presents version 3.6.0, while package.json ships version 3.7.0. This guide reports both exactly as they stand rather than choosing between them.

Fork the repository, then open the session service linked in the README SCAN QR section, x-bot-md-qr.koyeb.app. Both server buttons point at that one address. Checked for this guide, the service loads and asks you to sign in with GitHub and hold a fork of the repository, after which it offers QR pairing and a pair code option.

In two places, neither of them a plain public pairing website. The hosted session service now offers a pair code option beside its QR route, behind its GitHub sign in and fork requirement. Separately, the developer X-MD-PAIR repository provides an eight character pairing code service with MongoDB storage and Session ID delivery by WhatsApp message, but it is source code you host yourself; its README publishes no hosted instance.

The README publishes no command list, no command categories and no prefix, so this guide publishes none. The repository plugins folder contains files for areas such as menus, downloading and groups, but any command list for X BOT MD found elsewhere does not come from the project README this guide could check.

Panel hosting through the repository wiki guide, Heroku through a template link, Koyeb through a prefilled deploy link whose fields include SESSION_ID, WORK_TYPE, HANDLERS, BOT_INFO, SUDO, STICKER_DATA, DATABASE_URL and KOYEB_API_KEY, and Render, which asks for a DATABASE_URL and a Render API key before deploying.

The records disagree. The LICENSE file in the repository carries the full GNU GPL v3 text and the GitHub API detects GPL-3.0, while the license field of package.json reads ISC. This guide reports both signals and names no single license for the bot. The separate X MD Pair repository carries an MIT LICENSE file.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the X BOT MD records that could be opened on the last verified date: the original repository at its current Aswin-Sparky address, reached through the redirect from its former A-S-W-I-N-S-P-A-R-K-Y address and read through the GitHub API and its raw files, including its README with the raw links behind its session and deployment buttons, its LICENSE file, package.json, config.js and its full repository tree, together with the repository wiki panel guide, the session service the README links, which was opened and found live behind a GitHub sign in and fork requirement, and the separate X-MD-PAIR repository with its README and LICENSE file. On that date the version records disagreed between 3.6.0 and 3.7.0 and the license records disagreed between the GPL v3 LICENSE file and the ISC package field, as this guide records. Where the records publish nothing, this guide says so instead of filling the gap.

AHMED X provides this article for educational and informational purposes only. AHMED X is not the developer or owner of XBOT MD and does not claim any partnership or official affiliation with Aswin Sparky 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

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

ZOKOU MD, also known as Zokou 2.0, is a third party WhatsApp Multi Device bot project by Djalega++ and Monkey D Luffy, documented in a French language README in its original GitHub repository. That repository is live today and was read in the original French for this guide: it documents the feature list, links one session website, and gives Heroku and Koyeb deployment routes. The session website was opened again for this guide and its QR route loads, while the pairing code destination it links out to returns a 404 error, and the README Heroku button in fact templates a different repository, so this guide states the present day condition of every route plainly.

Read the guide
Guide

MD Bot WhatsApp: Complete Beginner Guide to Features, Session ID and Deployment

An MD bot WhatsApp application is an automated WhatsApp bot that connects to an account using WhatsApp Multi Device functionality. These bots can help users automate messages, manage groups, download media, create stickers, and perform other tasks through WhatsApp commands. Many WhatsApp MD bots are available as open source JavaScript projects. Beginners can choose a project, connect their WhatsApp account using a QR code or pairing code, and run the bot on a computer, VPS, or supported cloud hosting service.

Read the guide
Guide

WhatsApp MD Bot: Types, Features and How to Choose the Best One

A WhatsApp MD bot is an automated application that connects to a WhatsApp account through Multi Device functionality. These bots are available in different categories, and each category is designed for a different purpose. Some WhatsApp MD bots focus on group management, while others provide media downloading, AI assistance, entertainment commands, or simple automatic replies.

Read the guide
Guide

MD WhatsApp Bot: Complete Guide to QR Code, Pairing Code and Session ID

Connecting an MD WhatsApp bot to your WhatsApp account is one of the most important steps when setting up a bot. Without successful authentication, the bot cannot establish its WhatsApp connection or process messages. Most WhatsApp MD bots use linked device authentication. Depending on the project, you may connect through a QR code or a pairing code and then use the generated session credentials to keep the bot connected.

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