BranchesTags

Repository files navigation

WhatsApp API with Bearer Token Authentication

A RESTful API for sending WhatsApp messages with bearer token authentication using the whatsapp-web.js library.

Requirements

  • Node.js (v14 or higher)
  • NPM

Installation

  1. Clone the repository
  2. Install dependencies: 
    npm install
  3. Create a .env file with the following variables: 
    PORT=3000
API_TOKEN=your_example_token

Startup

npm start

For development with automatic restart:

npm run dev

On first launch, a QR code will be generated in the terminal that you'll need to scan with WhatsApp on your phone for authentication.

Docker Deployment

Build and run with Docker

  1. Build the Docker image:

    docker build -t whatsapp-api .

  2. Run the container:

    docker run -p 3000:3000 -e API_TOKEN=your-secure-token --name whatsapp-api -v whatsapp-auth:/app/.wwebjs_auth whatsapp-api

Using Docker Compose (Recommended)

  1. Customize the environment variables in docker-compose.yml if needed
  2. Start the services: 
    docker-compose up -d
  3. View logs to scan the QR code when first starting: 
    docker-compose logs -f

The session data is persisted in a Docker volume, so you won't need to scan the QR code again after restarts.

Session Persistence

The API automatically maintains the WhatsApp session even after server restart:

  • The session is saved in the .wwebjs_auth folder
  • You don't need to scan the QR code every time you restart the server
  • To manually disconnect, a specific endpoint is available (/api/logout)

Anti-Ban System

To avoid WhatsApp bans, the API implements a queue system that limits message sending:

  • Maximum one message every 30-60 seconds (random wait time)
  • Messages are queued and sent automatically respecting these limits
  • API responses include information about the queue and estimated wait times

API Endpoints

Service Status

GET /api/status

Required header:

Authorization: Bearer <token-from-env-file>

Response: Service status including queue and WhatsApp connection information.

Send Message

POST /api/send

Required header:

Authorization: Bearer <token-from-env-file>
Content-Type: application/json

Body:

{
"number": "391234567890", "message": "Hi, this is a test message",
"options": {} // Additional options (optional)
}

Note:

  • The number must be in international format without '+' or other special characters
  • The message will be queued and sent respecting the time limits
  • The response will include information about the estimated wait time

Queue Status

GET /api/queue

Required header:

Authorization: Bearer <token-from-env-file>

Response: Information about the message queue, including the number of messages waiting.

WhatsApp Disconnection

POST /api/logout

Required header:

Authorization: Bearer <token-from-env-file>

Response: Confirmation of disconnection from WhatsApp. You'll need to scan the QR code again to reconnect.

Usage Examples with cURL

Get Service Status

curl -X GET http://localhost:3000/api/status \
-H "Authorization: Bearer <token-from-env-file>"

Send a Message

curl -X POST http://localhost:3000/api/send \
-H "Authorization: Bearer <token-from-env-file>" \
-H "Content-Type: application/json" \
-d '{"number":"391234567890","message":"Test message"}'

Check Queue Status

curl -X GET http://localhost:3000/api/queue \
-H "Authorization: Bearer <token-from-env-file>"

Disconnect WhatsApp

curl -X POST http://localhost:3000/api/logout \
-H "Authorization: Bearer <token-from-env-file>"

About

No description, website, or topics provided.

Resources

Readme
Activity
Custom properties

Stars

1 star

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
BranchesTags
Repository files navigation
WhatsApp API with Bearer Token Authentication
A RESTful API for sending WhatsApp messages with bearer token authentication using the whatsapp-web.js library.
Requirements
  • Node.js (v14 or higher)
  • NPM
Installation
  1. Clone the repository
  2. Install dependencies:

    npm install

  3. Create a .env file with the following variables:

    PORT=3000
API_TOKEN=your_example_token

Startup
npm start

For development with automatic restart:
npm run dev

On first launch, a QR code will be generated in the terminal that you'll need to scan with WhatsApp on your phone for authentication.
Docker Deployment
Build and run with Docker
  1. Build the Docker image:
    docker build -t whatsapp-api .

  2. Run the container:
    docker run -p 3000:3000 -e API_TOKEN=your-secure-token --name whatsapp-api -v whatsapp-auth:/app/.wwebjs_auth whatsapp-api

Using Docker Compose (Recommended)
  1. Customize the environment variables in docker-compose.yml if needed
  2. Start the services:

    docker-compose up -d

  3. View logs to scan the QR code when first starting:

    docker-compose logs -f

The session data is persisted in a Docker volume, so you won't need to scan the QR code again after restarts.
Session Persistence
The API automatically maintains the WhatsApp session even after server restart:
  • The session is saved in the .wwebjs_auth folder
  • You don't need to scan the QR code every time you restart the server
  • To manually disconnect, a specific endpoint is available (/api/logout)
Anti-Ban System
To avoid WhatsApp bans, the API implements a queue system that limits message sending:
  • Maximum one message every 30-60 seconds (random wait time)
  • Messages are queued and sent automatically respecting these limits
  • API responses include information about the queue and estimated wait times
API Endpoints
Service Status
GET /api/status

Required header:
Authorization: Bearer <token-from-env-file>

Response: Service status including queue and WhatsApp connection information.
Send Message
POST /api/send

Required header:
Authorization: Bearer <token-from-env-file>
Content-Type: application/json

Body:
{
"number": "391234567890", "message": "Hi, this is a test message",
"options": {} // Additional options (optional)
}
Note:
  • The number must be in international format without '+' or other special characters
  • The message will be queued and sent respecting the time limits
  • The response will include information about the estimated wait time
Queue Status
GET /api/queue

Required header:
Authorization: Bearer <token-from-env-file>

Response: Information about the message queue, including the number of messages waiting.
WhatsApp Disconnection
POST /api/logout

Required header:
Authorization: Bearer <token-from-env-file>

Response: Confirmation of disconnection from WhatsApp. You'll need to scan the QR code again to reconnect.
Usage Examples with cURL
Get Service Status
curl -X GET http://localhost:3000/api/status \
-H "Authorization: Bearer <token-from-env-file>"

Send a Message
curl -X POST http://localhost:3000/api/send \
-H "Authorization: Bearer <token-from-env-file>" \
-H "Content-Type: application/json" \
-d '{"number":"391234567890","message":"Test message"}'

Check Queue Status
curl -X GET http://localhost:3000/api/queue \
-H "Authorization: Bearer <token-from-env-file>"

Disconnect WhatsApp
curl -X POST http://localhost:3000/api/logout \
-H "Authorization: Bearer <token-from-env-file>"

About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
WhatsApp API with Bearer Token Authentication
A RESTful API for sending WhatsApp messages with bearer token authentication using the whatsapp-web.js library.
Requirements
  • Node.js (v14 or higher)
  • NPM
Installation
  1. Clone the repository
  2. Install dependencies:

    npm install

  3. Create a .env file with the following variables:

    PORT=3000
API_TOKEN=your_example_token

Startup
npm start

For development with automatic restart:
npm run dev

On first launch, a QR code will be generated in the terminal that you'll need to scan with WhatsApp on your phone for authentication.
Docker Deployment
Build and run with Docker
  1. Build the Docker image:
    docker build -t whatsapp-api .

  2. Run the container:
    docker run -p 3000:3000 -e API_TOKEN=your-secure-token --name whatsapp-api -v whatsapp-auth:/app/.wwebjs_auth whatsapp-api

Using Docker Compose (Recommended)
  1. Customize the environment variables in docker-compose.yml if needed
  2. Start the services:

    docker-compose up -d

  3. View logs to scan the QR code when first starting:

    docker-compose logs -f

The session data is persisted in a Docker volume, so you won't need to scan the QR code again after restarts.
Session Persistence
The API automatically maintains the WhatsApp session even after server restart:
  • The session is saved in the .wwebjs_auth folder
  • You don't need to scan the QR code every time you restart the server
  • To manually disconnect, a specific endpoint is available (/api/logout)
Anti-Ban System
To avoid WhatsApp bans, the API implements a queue system that limits message sending:
  • Maximum one message every 30-60 seconds (random wait time)
  • Messages are queued and sent automatically respecting these limits
  • API responses include information about the queue and estimated wait times
API Endpoints
Service Status
GET /api/status

Required header:
Authorization: Bearer <token-from-env-file>

Response: Service status including queue and WhatsApp connection information.
Send Message
POST /api/send

Required header:
Authorization: Bearer <token-from-env-file>
Content-Type: application/json

Body:
{
"number": "391234567890", "message": "Hi, this is a test message",
"options": {} // Additional options (optional)
}
Note:
  • The number must be in international format without '+' or other special characters
  • The message will be queued and sent respecting the time limits
  • The response will include information about the estimated wait time
Queue Status
GET /api/queue

Required header:
Authorization: Bearer <token-from-env-file>

Response: Information about the message queue, including the number of messages waiting.
WhatsApp Disconnection
POST /api/logout

Required header:
Authorization: Bearer <token-from-env-file>

Response: Confirmation of disconnection from WhatsApp. You'll need to scan the QR code again to reconnect.
Usage Examples with cURL
Get Service Status
curl -X GET http://localhost:3000/api/status \
-H "Authorization: Bearer <token-from-env-file>"

Send a Message
curl -X POST http://localhost:3000/api/send \
-H "Authorization: Bearer <token-from-env-file>" \
-H "Content-Type: application/json" \
-d '{"number":"391234567890","message":"Test message"}'

Check Queue Status
curl -X GET http://localhost:3000/api/queue \
-H "Authorization: Bearer <token-from-env-file>"

Disconnect WhatsApp
curl -X POST http://localhost:3000/api/logout \
-H "Authorization: Bearer <token-from-env-file>"

About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
WhatsApp API with Bearer Token Authentication
A RESTful API for sending WhatsApp messages with bearer token authentication using the whatsapp-web.js library.
Requirements
  • Node.js (v14 or higher)
  • NPM
Installation
  1. Clone the repository
  2. Install dependencies:

    npm install

  3. Create a .env file with the following variables:

    PORT=3000
API_TOKEN=your_example_token

Startup
npm start

For development with automatic restart:
npm run dev

On first launch, a QR code will be generated in the terminal that you'll need to scan with WhatsApp on your phone for authentication.
Docker Deployment
Build and run with Docker
  1. Build the Docker image:
    docker build -t whatsapp-api .

  2. Run the container:
    docker run -p 3000:3000 -e API_TOKEN=your-secure-token --name whatsapp-api -v whatsapp-auth:/app/.wwebjs_auth whatsapp-api

Using Docker Compose (Recommended)
  1. Customize the environment variables in docker-compose.yml if needed
  2. Start the services:

    docker-compose up -d

  3. View logs to scan the QR code when first starting:

    docker-compose logs -f

The session data is persisted in a Docker volume, so you won't need to scan the QR code again after restarts.
Session Persistence
The API automatically maintains the WhatsApp session even after server restart:
  • The session is saved in the .wwebjs_auth folder
  • You don't need to scan the QR code every time you restart the server
  • To manually disconnect, a specific endpoint is available (/api/logout)
Anti-Ban System
To avoid WhatsApp bans, the API implements a queue system that limits message sending:
  • Maximum one message every 30-60 seconds (random wait time)
  • Messages are queued and sent automatically respecting these limits
  • API responses include information about the queue and estimated wait times
API Endpoints
Service Status
GET /api/status

Required header:
Authorization: Bearer <token-from-env-file>

Response: Service status including queue and WhatsApp connection information.
Send Message
POST /api/send

Required header:
Authorization: Bearer <token-from-env-file>
Content-Type: application/json

Body:
{
"number": "391234567890", "message": "Hi, this is a test message",
"options": {} // Additional options (optional)
}
Note:
  • The number must be in international format without '+' or other special characters
  • The message will be queued and sent respecting the time limits
  • The response will include information about the estimated wait time
Queue Status
GET /api/queue

Required header:
Authorization: Bearer <token-from-env-file>

Response: Information about the message queue, including the number of messages waiting.
WhatsApp Disconnection
POST /api/logout

Required header:
Authorization: Bearer <token-from-env-file>

Response: Confirmation of disconnection from WhatsApp. You'll need to scan the QR code again to reconnect.
Usage Examples with cURL
Get Service Status
curl -X GET http://localhost:3000/api/status \
-H "Authorization: Bearer <token-from-env-file>"

Send a Message
curl -X POST http://localhost:3000/api/send \
-H "Authorization: Bearer <token-from-env-file>" \
-H "Content-Type: application/json" \
-d '{"number":"391234567890","message":"Test message"}'

Check Queue Status
curl -X GET http://localhost:3000/api/queue \
-H "Authorization: Bearer <token-from-env-file>"

Disconnect WhatsApp
curl -X POST http://localhost:3000/api/logout \
-H "Authorization: Bearer <token-from-env-file>"

About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
BranchesTags
Repository files navigation
WhatsApp API with Bearer Token Authentication
A RESTful API for sending WhatsApp messages with bearer token authentication using the whatsapp-web.js library.
Requirements
  • Node.js (v14 or higher)
  • NPM
Installation
  1. Clone the repository
  2. Install dependencies:

    npm install

  3. Create a .env file with the following variables:

    PORT=3000
API_TOKEN=your_example_token

Startup
npm start

For development with automatic restart:
npm run dev

On first launch, a QR code will be generated in the terminal that you'll need to scan with WhatsApp on your phone for authentication.
Docker Deployment
Build and run with Docker
  1. Build the Docker image:
    docker build -t whatsapp-api .

  2. Run the container:
    docker run -p 3000:3000 -e API_TOKEN=your-secure-token --name whatsapp-api -v whatsapp-auth:/app/.wwebjs_auth whatsapp-api

Using Docker Compose (Recommended)
  1. Customize the environment variables in docker-compose.yml if needed
  2. Start the services:

    docker-compose up -d

  3. View logs to scan the QR code when first starting:

    docker-compose logs -f

The session data is persisted in a Docker volume, so you won't need to scan the QR code again after restarts.
Session Persistence
The API automatically maintains the WhatsApp session even after server restart:
  • The session is saved in the .wwebjs_auth folder
  • You don't need to scan the QR code every time you restart the server
  • To manually disconnect, a specific endpoint is available (/api/logout)
Anti-Ban System
To avoid WhatsApp bans, the API implements a queue system that limits message sending:
  • Maximum one message every 30-60 seconds (random wait time)
  • Messages are queued and sent automatically respecting these limits
  • API responses include information about the queue and estimated wait times
API Endpoints
Service Status
GET /api/status

Required header:
Authorization: Bearer <token-from-env-file>

Response: Service status including queue and WhatsApp connection information.
Send Message
POST /api/send

Required header:
Authorization: Bearer <token-from-env-file>
Content-Type: application/json

Body:
{
"number": "391234567890", "message": "Hi, this is a test message",
"options": {} // Additional options (optional)
}
Note:
  • The number must be in international format without '+' or other special characters
  • The message will be queued and sent respecting the time limits
  • The response will include information about the estimated wait time
Queue Status
GET /api/queue

Required header:
Authorization: Bearer <token-from-env-file>

Response: Information about the message queue, including the number of messages waiting.
WhatsApp Disconnection
POST /api/logout

Required header:
Authorization: Bearer <token-from-env-file>

Response: Confirmation of disconnection from WhatsApp. You'll need to scan the QR code again to reconnect.
Usage Examples with cURL
Get Service Status
curl -X GET http://localhost:3000/api/status \
-H "Authorization: Bearer <token-from-env-file>"

Send a Message
curl -X POST http://localhost:3000/api/send \
-H "Authorization: Bearer <token-from-env-file>" \
-H "Content-Type: application/json" \
-d '{"number":"391234567890","message":"Test message"}'

Check Queue Status
curl -X GET http://localhost:3000/api/queue \
-H "Authorization: Bearer <token-from-env-file>"

Disconnect WhatsApp
curl -X POST http://localhost:3000/api/logout \
-H "Authorization: Bearer <token-from-env-file>"

About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
WhatsApp API with Bearer Token Authentication
A RESTful API for sending WhatsApp messages with bearer token authentication using the whatsapp-web.js library.
Requirements
  • Node.js (v14 or higher)
  • NPM
Installation
  1. Clone the repository
  2. Install dependencies:

    npm install

  3. Create a .env file with the following variables:

    PORT=3000
API_TOKEN=your_example_token

Startup
npm start

For development with automatic restart:
npm run dev

On first launch, a QR code will be generated in the terminal that you'll need to scan with WhatsApp on your phone for authentication.
Docker Deployment
Build and run with Docker
  1. Build the Docker image:
    docker build -t whatsapp-api .

  2. Run the container:
    docker run -p 3000:3000 -e API_TOKEN=your-secure-token --name whatsapp-api -v whatsapp-auth:/app/.wwebjs_auth whatsapp-api

Using Docker Compose (Recommended)
  1. Customize the environment variables in docker-compose.yml if needed
  2. Start the services:

    docker-compose up -d

  3. View logs to scan the QR code when first starting:

    docker-compose logs -f

The session data is persisted in a Docker volume, so you won't need to scan the QR code again after restarts.
Session Persistence
The API automatically maintains the WhatsApp session even after server restart:
  • The session is saved in the .wwebjs_auth folder
  • You don't need to scan the QR code every time you restart the server
  • To manually disconnect, a specific endpoint is available (/api/logout)
Anti-Ban System
To avoid WhatsApp bans, the API implements a queue system that limits message sending:
  • Maximum one message every 30-60 seconds (random wait time)
  • Messages are queued and sent automatically respecting these limits
  • API responses include information about the queue and estimated wait times
API Endpoints
Service Status
GET /api/status

Required header:
Authorization: Bearer <token-from-env-file>

Response: Service status including queue and WhatsApp connection information.
Send Message
POST /api/send

Required header:
Authorization: Bearer <token-from-env-file>
Content-Type: application/json

Body:
{
"number": "391234567890", "message": "Hi, this is a test message",
"options": {} // Additional options (optional)
}
Note:
  • The number must be in international format without '+' or other special characters
  • The message will be queued and sent respecting the time limits
  • The response will include information about the estimated wait time
Queue Status
GET /api/queue

Required header:
Authorization: Bearer <token-from-env-file>

Response: Information about the message queue, including the number of messages waiting.
WhatsApp Disconnection
POST /api/logout

Required header:
Authorization: Bearer <token-from-env-file>

Response: Confirmation of disconnection from WhatsApp. You'll need to scan the QR code again to reconnect.
Usage Examples with cURL
Get Service Status
curl -X GET http://localhost:3000/api/status \
-H "Authorization: Bearer <token-from-env-file>"

Send a Message
curl -X POST http://localhost:3000/api/send \
-H "Authorization: Bearer <token-from-env-file>" \
-H "Content-Type: application/json" \
-d '{"number":"391234567890","message":"Test message"}'

Check Queue Status
curl -X GET http://localhost:3000/api/queue \
-H "Authorization: Bearer <token-from-env-file>"

Disconnect WhatsApp
curl -X POST http://localhost:3000/api/logout \
-H "Authorization: Bearer <token-from-env-file>"

About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
BranchesTags
Repository files navigation
WhatsApp API with Bearer Token Authentication
A RESTful API for sending WhatsApp messages with bearer token authentication using the whatsapp-web.js library.
Requirements
  • Node.js (v14 or higher)
  • NPM
Installation
  1. Clone the repository
  2. Install dependencies:

    npm install

  3. Create a .env file with the following variables:

    PORT=3000
API_TOKEN=your_example_token

Startup
npm start

For development with automatic restart:
npm run dev

On first launch, a QR code will be generated in the terminal that you'll need to scan with WhatsApp on your phone for authentication.
Docker Deployment
Build and run with Docker
  1. Build the Docker image:
    docker build -t whatsapp-api .

  2. Run the container:
    docker run -p 3000:3000 -e API_TOKEN=your-secure-token --name whatsapp-api -v whatsapp-auth:/app/.wwebjs_auth whatsapp-api

Using Docker Compose (Recommended)
  1. Customize the environment variables in docker-compose.yml if needed
  2. Start the services:

    docker-compose up -d

  3. View logs to scan the QR code when first starting:

    docker-compose logs -f

The session data is persisted in a Docker volume, so you won't need to scan the QR code again after restarts.
Session Persistence
The API automatically maintains the WhatsApp session even after server restart:
  • The session is saved in the .wwebjs_auth folder
  • You don't need to scan the QR code every time you restart the server
  • To manually disconnect, a specific endpoint is available (/api/logout)
Anti-Ban System
To avoid WhatsApp bans, the API implements a queue system that limits message sending:
  • Maximum one message every 30-60 seconds (random wait time)
  • Messages are queued and sent automatically respecting these limits
  • API responses include information about the queue and estimated wait times
API Endpoints
Service Status
GET /api/status

Required header:
Authorization: Bearer <token-from-env-file>

Response: Service status including queue and WhatsApp connection information.
Send Message
POST /api/send

Required header:
Authorization: Bearer <token-from-env-file>
Content-Type: application/json

Body:
{
"number": "391234567890", "message": "Hi, this is a test message",
"options": {} // Additional options (optional)
}
Note:
  • The number must be in international format without '+' or other special characters
  • The message will be queued and sent respecting the time limits
  • The response will include information about the estimated wait time
Queue Status
GET /api/queue

Required header:
Authorization: Bearer <token-from-env-file>

Response: Information about the message queue, including the number of messages waiting.
WhatsApp Disconnection
POST /api/logout

Required header:
Authorization: Bearer <token-from-env-file>

Response: Confirmation of disconnection from WhatsApp. You'll need to scan the QR code again to reconnect.
Usage Examples with cURL
Get Service Status
curl -X GET http://localhost:3000/api/status \
-H "Authorization: Bearer <token-from-env-file>"

Send a Message
curl -X POST http://localhost:3000/api/send \
-H "Authorization: Bearer <token-from-env-file>" \
-H "Content-Type: application/json" \
-d '{"number":"391234567890","message":"Test message"}'

Check Queue Status
curl -X GET http://localhost:3000/api/queue \
-H "Authorization: Bearer <token-from-env-file>"

Disconnect WhatsApp
curl -X POST http://localhost:3000/api/logout \
-H "Authorization: Bearer <token-from-env-file>"

About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
BranchesTags
Repository files navigation
WhatsApp API with Bearer Token Authentication
A RESTful API for sending WhatsApp messages with bearer token authentication using the whatsapp-web.js library.
Requirements
  • Node.js (v14 or higher)
  • NPM
Installation
  1. Clone the repository
  2. Install dependencies:

    npm install

  3. Create a .env file with the following variables:

    PORT=3000
API_TOKEN=your_example_token

Startup
npm start

For development with automatic restart:
npm run dev

On first launch, a QR code will be generated in the terminal that you'll need to scan with WhatsApp on your phone for authentication.
Docker Deployment
Build and run with Docker
  1. Build the Docker image:
    docker build -t whatsapp-api .

  2. Run the container:
    docker run -p 3000:3000 -e API_TOKEN=your-secure-token --name whatsapp-api -v whatsapp-auth:/app/.wwebjs_auth whatsapp-api

Using Docker Compose (Recommended)
  1. Customize the environment variables in docker-compose.yml if needed
  2. Start the services:

    docker-compose up -d

  3. View logs to scan the QR code when first starting:

    docker-compose logs -f

The session data is persisted in a Docker volume, so you won't need to scan the QR code again after restarts.
Session Persistence
The API automatically maintains the WhatsApp session even after server restart:
  • The session is saved in the .wwebjs_auth folder
  • You don't need to scan the QR code every time you restart the server
  • To manually disconnect, a specific endpoint is available (/api/logout)
Anti-Ban System
To avoid WhatsApp bans, the API implements a queue system that limits message sending:
  • Maximum one message every 30-60 seconds (random wait time)
  • Messages are queued and sent automatically respecting these limits
  • API responses include information about the queue and estimated wait times
API Endpoints
Service Status
GET /api/status

Required header:
Authorization: Bearer <token-from-env-file>

Response: Service status including queue and WhatsApp connection information.
Send Message
POST /api/send

Required header:
Authorization: Bearer <token-from-env-file>
Content-Type: application/json

Body:
{
"number": "391234567890", "message": "Hi, this is a test message",
"options": {} // Additional options (optional)
}
Note:
  • The number must be in international format without '+' or other special characters
  • The message will be queued and sent respecting the time limits
  • The response will include information about the estimated wait time
Queue Status
GET /api/queue

Required header:
Authorization: Bearer <token-from-env-file>

Response: Information about the message queue, including the number of messages waiting.
WhatsApp Disconnection
POST /api/logout

Required header:
Authorization: Bearer <token-from-env-file>

Response: Confirmation of disconnection from WhatsApp. You'll need to scan the QR code again to reconnect.
Usage Examples with cURL
Get Service Status
curl -X GET http://localhost:3000/api/status \
-H "Authorization: Bearer <token-from-env-file>"

Send a Message
curl -X POST http://localhost:3000/api/send \
-H "Authorization: Bearer <token-from-env-file>" \
-H "Content-Type: application/json" \
-d '{"number":"391234567890","message":"Test message"}'

Check Queue Status
curl -X GET http://localhost:3000/api/queue \
-H "Authorization: Bearer <token-from-env-file>"

Disconnect WhatsApp
curl -X POST http://localhost:3000/api/logout \
-H "Authorization: Bearer <token-from-env-file>"

About
No description, website, or topics provided.
Resources
Readme
Activity
Custom properties
Stars
1 star
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages