# chrishubert/whatsapp-api

This project is a REST API wrapper for the whatsapp-web.js library, providing an easy-to-use interface to interact with the WhatsApp Web platform.

Repository: https://github.com/chrishubert/whatsapp-api
Canonical: https://ross.abutalabs.com/products/whatsapp-api
Homepage: https://www.christophehubert.com
Language: JavaScript
License: NOASSERTION
License Family: other
Topics: api-rest, docker, whatsapp, api, whatsapp-api, whatsapp-automation, whatsapp-bot, whatsapp-web-api
Archived: true
Last push: 2025-12-19T00:27:24+00:00

## Health v2 (maintenance only)
Score: 10/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 57, release rhythm 8, longevity 88
- inputs: {"age_days": 1239, "days_push": 258, "days_rel": 688, "gap_med": null, "n_releases_24m": 1}
- flags: archived, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1445, forks 553 (observed 2026-08-28T04:04:45.079893+00:00)

## What it is
A REST API wrapper around the whatsapp-web.js library that lets you send messages, manage sessions, and receive callbacks by interacting with WhatsApp Web through a Dockerized Node.js service. The original project is deprecated and no longer maintained, with users directed to the avoylenko/wwebjs-api fork.

## Use cases
- send whatsapp messages from a rest api
- run a whatsapp bot without the official business api
- integrate whatsapp into a non-nodejs application
- receive whatsapp message callbacks via webhooks
- self-host a whatsapp gateway in docker
- automate whatsapp notifications for my app

## When to choose
- you need a quick self-hosted WhatsApp REST gateway and accept the ban risk
- you want to use the maintained fork of this wrapper
- your stack is not Node.js and you need an HTTP interface to WhatsApp Web

## When to avoid
- you need a maintained or officially supported solution
- you cannot risk your WhatsApp account being banned for using an unofficial client
- you require compliance with WhatsApp's terms of service

## Facets
- artifact type: service
- maturity: abandoned
- function: http-server, api-framework, chatbot, webhook
- domain: messaging-platforms, apis, self-hosted
- platform: self-hosted
- tags: whatsapp, whatsapp-web-js, rest-api-wrapper, unofficial-api, deprecated, docker-compose, messaging-automation, automation, nodejs, docker, web-server

## Member repositories
- chrishubert/whatsapp-api (main) score 10

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:45.079893+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:36:13.631655+00:00, confidence not recorded.
  - readme: https://github.com/chrishubert/whatsapp-api (fetched 2026-08-28T04:04:45.079893+00:00, sha 965fbecd172d)
  - homepage: https://www.christophehubert.com (fetched 2026-08-29T11:46:28.040869+00:00, sha febc91567e2b)
  - site_page: https://www.christophehubert.com/about (fetched 2026-08-29T11:46:28.049670+00:00, sha 4ac1ac85e898)
- Data as of 2026-08-30T08:39:29.467469+00:00.