Security News
PyPI Introduces Digital Attestations to Strengthen Python Package Security
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
whatsapp-api-js
Advanced tools
A TypeScript server agnostic Whatsapp's Official API framework.
First, you need a Facebook app with the Whatsapp API activated. You can create your first app following this steps. Get the API token, either a temporal or a permanent one.
In your server you can install the module using npm:
npm install whatsapp-api-js
Now you can write code like this:
import WhatsAppAPI from "whatsapp-api-js";
import { Text, Image, Document } from "whatsapp-api-js/messages";
import * as Contacts from "whatsapp-api-js/messages/contacts";
// Kind reminder to not hardcode your token and secret
const TOKEN = "YOUR_TOKEN";
const APP_SECRET = "YOUR_SECRET";
const Whatsapp = new WhatsAppAPI({ token: TOKEN, appSecret: APP_SECRET });
// Assuming post is called on a POST request to your server
function post(e) {
// The handlers work with any middleware, as long as you pass the correct data
return Whatsapp.post(JSON.parse(e.data), e.data, e.headers["X-Hub-Signature-256"]);
}
Whatsapp.on.message = ({ phoneID, from, message, name, raw }) => {
console.log(`User ${name} (${from}) sent to bot ${phoneID} ${JSON.stringify(message)}`);
let promise;
if (message.type === "text") {
promise = Whatsapp.sendMessage(phoneID, from, new Text(`*${name}* said:\n\n${message.text.body}`), message.id);
}
if (message.type === "image") {
promise = Whatsapp.sendMessage(phoneID, from, new Image(message.image.id, true, `Nice photo, ${name}`));
}
if (message.type === "document") {
promise = Whatsapp.sendMessage(phoneID, from, new Document(message.document.id, true, undefined, "Our document"));
}
if (message.type === "contacts") {
promise = Whatsapp.sendMessage(phoneID, from, new Contacts.Contacts(
[
new Contacts.Name(name, "First name", "Last name"),
new Contacts.Phone(phone),
new Contacts.Birthday("2022", "04", "25"),
],
[
new Contacts.Name("John", "First name", "Last name"),
new Contacts.Organization("Company", "Department", "Title"),
new Contacts.Url("https://www.google.com", "WORK"),
]
));
}
console.log(await promise ?? "There are more types of messages, such as locations, templates, interactives, reactions and all the other media types.");
Whatsapp.markAsRead(phoneID, message.id);
};
Whatsapp.on.sent = ({ phoneID, to, message, raw }) => {
console.log(`Bot ${phoneID} sent to user ${to} ${message}\n\n${JSON.stringify(raw)}`);
};
To recieve the post requests on message, you must setup the webhook at your Facebook app. While setting up, you will be asked a Verify Token. This can be any string you want.
The app also has a GET wizard for the webhook authentication:
import WhatsAppAPI from "whatsapp-api-js";
const TOKEN = "YOUR_TOKEN";
const APP_SECRET = "YOUR_SECRET";
const VERIFY_TOKEN = "YOUR_VERIFY_TOKEN";
const Whatsapp = new WhatsAppAPI({
token: TOKEN,
appSecret: APP_SECRET,
webhookVerifyToken: VERIFY_TOKEN
});
// Assuming get is called on a GET request to your server
function get(e) {
return Whatsapp.get(JSON.parse(e.params));
}
Once you are done, click administrate, and set the webhook to subscribe to messages only. There might be a future update to support the other types of subscriptions.
And that's it! Now you have a functioning Whatsapp Bot connected to your server.
To know what changed between updates, check out the releases on Github.
The code is server agnostic, which allows it to work on most environments.
If using ESM, you can import the module like this:
import WhatsAppAPI from "whatsapp-api-js";
If using CommonJS, you can require the package:
const WhatsAppAPI = require("whatsapp-api-js");
With the release of Deno 1.25.0, now you can import npm modules directly to Deno. It's really simple to use:
import WhatsAppAPI from "npm:whatsapp-api-js";
If you want to use prior versions of Deno, use https://esm.sh/whatsapp-api-js to import the code.
Bun should also work by running:
bun install whatsapp-api-js
import WhatsAppAPI from "whatsapp-api-js";
HTML module example:
<script type="module">
import WhatsAppAPI from "https://esm.sh/whatsapp-api-js";
<!-- Please, never use your API tokens in a website, use this method wisely -->
</script>
The module was rewritten in TypeScript, and most of the import syntax changed. CommonJS is still supported.
Examples:
// ESM
import WhatsAppAPI from "whatsapp-api-js";
import { Text, Image, Document } from "whatsapp-api-js/messages";
import Location from "whatsapp-api-js/messages/location";
// CommonJS
const WhatsAppAPI = require("whatsapp-api-js");
const { Text, Image, Document } = require("whatsapp-api-js/messages");
const Location = require("whatsapp-api-js/messages/location");
The default undici fallback was also removed, and the module now uses the enviroment fetch implementation. Ponyfilling is still possible via the new parameter at the WhatsAppAPI() constructor:
import WhatsAppAPI from "whatsapp-api-js";
import { fetch } from "undici";
const Whatsapp = new WhatsAppAPI({
token: "YOUR_TOKEN_HERE",
appSecret: "YOUR_SECRET_HERE",
ponyfill: {
fetch
}
});
This change also restores the compatibility with previous Node.js versions, making the module more server agnostic.
The module changed from using "cross-fetch" to "undici" as the fallback fetch implementation in order to use FormData for the Media upload support, which is not (easily) available in "cross-fetch".
Although this change doesn't affect existing code, it forces the Node.js version to be at least 16. If the module is downloaded using a lower version, npm will throw an error.
With the release of cart support for Cloud API, some naming changes where made within the interactive's classes. The Section class, which was a component of the ActionList, was renamed to ListSection, to avoid confusion with the new ProductSection.
Since 0.6.0, the module will no longer return the raw fetch request, now it's internally parsed and returned.
This change was made in order to improve the logSentMessages function, as it can now log the server response too.
To get the raw request as before, you can use the parsed
property of the main object as follows.
const parsed = false;
const Whatsapp = new WhatsAppAPI("YOUR_TOKEN", undefined, parsed);
// All the API operations, like sendMessage, will now return the raw request.
// Keep in mind, now when using logSentMessage the id and response parameters will be undefined.
The lateset package documentation is available in whatsappapijs.web.app, and previous versions are available in secreto31126.github.io/whatsapp-api-js.
Install the latest beta realease with npm install whatsapp-api-js@beta
.
As any beta, it is 110% likely to break. I also use this tag to test npm releases.
Use it at your own risk.
Even though the code already supports all the message types, there's still a long way to go. I will keep updating it until I like how it works.
Also, if you are interested in Google App Script support, check out Secreto31126/whatsapp-api-google-app-script.
FAQs
A TypeScript server agnostic Whatsapp's Official API framework
The npm package whatsapp-api-js receives a total of 0 weekly downloads. As such, whatsapp-api-js popularity was classified as not popular.
We found that whatsapp-api-js demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.