WhaTools — WhatsApp tools

Generate a WhatsApp click-to-chat (wa.me) link with an optional phone number and pre-filled message. Runs locally; no message is sent.

{
  "type": "object",
  "properties": {
    "phone": {
      "type": "string",
      "description": "Recipient phone number in international format (digits only; optional). Omit to create a share link with no specific recipient."
    },
    "message": {
      "type": "string",
      "description": "The message to pre-fill in the chat (optional)."
    }
  },
  "required": [],
  "additionalProperties": false
}

Generate personalized WhatsApp click-to-chat (wa.me) links for a list of contacts from one message template. Everything uses a single {{…}} syntax: {{field}} placeholders are replaced per contact; {{field|fallback}} supplies a default for empty/missing fields; {{FirstName}} is derived from a name field; and {{option a|option b}} spintax (a group whose first option is not a field) picks one variation per contact (stable per number) so messages are not identical. Returns a JSON array of {phone, message, link}. Runs locally; no message is sent: each link opens WhatsApp with the text pre-filled and a human taps send.

{
  "type": "object",
  "properties": {
    "template": {
      "type": "string",
      "description": "Message template with {{field}} placeholders, e.g. 'Hello {{name}}, see you at {{time}}'. Supports {{field|fallback}} defaults, {{FirstName}} derived from a name field, and {{a|b|c}} spintax variation (a {{…}} group whose first option isn't a field). Placeholder matching is case-insensitive; WhatsApp formatting (*bold*, _italic_) is kept."
    },
    "contacts": {
      "type": "array",
      "maxItems": 500,
      "description": "Up to 500 contacts. Each needs a \"phone\" (international format, digits only) plus any placeholder fields as string properties.",
      "items": {
        "type": "object",
        "properties": {
          "phone": {
            "type": "string",
            "description": "Recipient phone number in international format (digits only)."
          }
        },
        "required": [
          "phone"
        ],
        "additionalProperties": {
          "type": "string"
        }
      }
    }
  },
  "required": [
    "template",
    "contacts"
  ],
  "additionalProperties": false
}

Validate and inspect a phone number with libphonenumber: whether it is valid (a real, allocated number) and/or possible (right length), its country, calling code, line type (mobile / landline / VoIP / toll-free / …) and every standard format (E.164, international, national) plus a wa.me link. Runs locally and offline. Does NOT check whether the number is registered on WhatsApp. There is no such API here.

{
  "type": "object",
  "properties": {
    "phone": {
      "type": "string",
      "description": "The phone number to validate. International format with a leading \"+\" is best; otherwise also pass `country`."
    },
    "country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2 country code (e.g. \"GB\", \"US\") assumed when the number has no country code. Optional."
    }
  },
  "required": [
    "phone"
  ],
  "additionalProperties": false
}

Generate a scannable QR code (as an SVG) for a WhatsApp click-to-chat link with an optional phone number and pre-filled message.

{
  "type": "object",
  "properties": {
    "phone": {
      "type": "string",
      "description": "Recipient phone number in international format (digits only; optional)."
    },
    "message": {
      "type": "string",
      "description": "The message to pre-fill in the chat (optional)."
    }
  },
  "required": [],
  "additionalProperties": false
}

Build embeddable "Share on WhatsApp" widget HTML (web and email variants) with a link preview card and a pre-filled message. Returns self-contained HTML.

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The URL being shared."
    },
    "title": {
      "type": "string",
      "description": "Title shown on the preview card."
    },
    "description": {
      "type": "string",
      "description": "Message text shown above the card (supports *bold*, _italic_, ~strike~)."
    },
    "thumbnail": {
      "type": "string",
      "description": "Preview image URL (optional)."
    },
    "domain": {
      "type": "string",
      "description": "Domain label shown on the card (optional)."
    },
    "buttonText": {
      "type": "string",
      "description": "Call-to-action button text (optional; defaults to \"Share on WhatsApp\")."
    },
    "buttonPlacement": {
      "type": "string",
      "enum": [
        "top",
        "bottom",
        "top-bottom"
      ],
      "description": "Where to place the share button relative to the card (optional)."
    },
    "includeCredit": {
      "type": "boolean",
      "description": "Append a small \"Widget by wha.tools\" credit line under the widget (optional; default false)."
    }
  },
  "required": [
    "url",
    "title",
    "description"
  ],
  "additionalProperties": false
}

Estimate the monthly WhatsApp Business (Cloud) API cost under Meta's per-message pricing (in effect since 1 July 2025). Given a country/market and monthly volumes of marketing, utility, authentication and (optionally) service messages, returns an itemized breakdown and total in USD. Marketing is always billed; utility and authentication are billed with volume-tier discounts in many markets. As of 1 October 2026 utility is billed even inside the customer-service window (previously free there), and service messages are billed at the utility rate with the first 1,000 per phone number each month free. Pass `service` to include them; omit it to leave service out. Runs locally. This is Meta's platform fee only: a BSP/provider adds its own fee on top, so treat it as a floor, not a quote.

{
  "type": "object",
  "properties": {
    "market": {
      "type": "string",
      "enum": [
        "AR",
        "BD",
        "BR",
        "CL",
        "CO",
        "EG",
        "FR",
        "DE",
        "HK",
        "HU",
        "IN",
        "ID",
        "IQ",
        "IL",
        "IT",
        "KZ",
        "KW",
        "MY",
        "MX",
        "MA",
        "NP",
        "NL",
        "NG",
        "OM",
        "PK",
        "PE",
        "PL",
        "QA",
        "RO",
        "RU",
        "SA",
        "SG",
        "ZA",
        "ES",
        "LK",
        "TR",
        "UA",
        "AE",
        "GB",
        "NA",
        "AFRICA",
        "APAC",
        "CEE",
        "LATAM",
        "MIDEAST",
        "WEUROPE",
        "OTHER"
      ],
      "description": "Recipient market as a 2-letter code (e.g. \"US\", \"IN\", \"BR\", \"GB\", \"DE\"), or \"ROW\" for rest of world. Rates vary widely by market."
    },
    "marketing": {
      "type": "number",
      "description": "Monthly count of marketing template messages (promotions, offers)."
    },
    "utility": {
      "type": "number",
      "description": "Monthly count of utility template messages (order updates, receipts, reminders)."
    },
    "authentication": {
      "type": "number",
      "description": "Monthly count of authentication template messages (one-time passcodes)."
    },
    "service": {
      "type": "number",
      "description": "Monthly count of service messages (free-form replies inside a customer-opened window). Optional. When given, the first 1,000 per phone number each month are free and the rest bill at the market's utility rate; omit to leave service out of the estimate."
    }
  },
  "required": [
    "market"
  ],
  "additionalProperties": false
}

Look up Meta's official WhatsApp Business (Cloud) API per-message rates from the site's dated rate card, the same figures the pricing calculator uses, so prefer this over recalling or guessing prices. Give a market to get one row, or omit it for every market in the chosen currency. Returns the current list price per template category (marketing, utility, authentication, and authentication-international where a market has one), the currency, the effective and last-verified dates, the source link and the CC BY licence. Optionally include the published volume-tier thresholds and rates for a single market. This is Meta's platform fee only: a BSP/provider adds its own fee on top, so treat it as a floor. Runs locally.

{
  "type": "object",
  "properties": {
    "market": {
      "type": "string",
      "enum": [
        "AR",
        "BD",
        "BR",
        "CL",
        "CO",
        "EG",
        "FR",
        "DE",
        "HK",
        "HU",
        "IN",
        "ID",
        "IQ",
        "IL",
        "IT",
        "KZ",
        "KW",
        "MY",
        "MX",
        "MA",
        "NP",
        "NL",
        "NG",
        "OM",
        "PK",
        "PE",
        "PL",
        "QA",
        "RO",
        "RU",
        "SA",
        "SG",
        "ZA",
        "ES",
        "LK",
        "TR",
        "UA",
        "AE",
        "GB",
        "NA",
        "AFRICA",
        "APAC",
        "CEE",
        "LATAM",
        "MIDEAST",
        "WEUROPE",
        "OTHER"
      ],
      "description": "Recipient market as a 2-letter code (e.g. \"US\"/\"NA\", \"IN\", \"BR\", \"GB\", \"DE\") or a \"Rest of\" region id. Omit to return the whole rate card for the chosen currency."
    },
    "currency": {
      "type": "string",
      "enum": [
        "USD",
        "EUR",
        "GBP",
        "INR",
        "IDR",
        "BRL",
        "MXN",
        "ARS",
        "COP",
        "AED",
        "SAR",
        "AUD",
        "MYR",
        "PEN",
        "CLP",
        "SGD"
      ],
      "description": "One of the 16 currencies Meta publishes a card in (USD, EUR, GBP, INR, IDR, BRL, MXN, ARS, COP, AED, SAR, AUD, MYR, PEN, CLP, SGD). Rates are stored per currency exactly as Meta prints them, never converted. Optional, default USD."
    },
    "include_tiers": {
      "type": "boolean",
      "description": "When a single market is given, also return that market's published volume-tier thresholds and per-band rates for utility and authentication. Ignored when no market is given. Optional, default false."
    }
  },
  "required": [],
  "additionalProperties": false
}

Look up WhatsApp's current limits and rules from the site's dated reference table: group and community size, broadcast lists, message and media/file sizes, character counts, forwarding, calls, Channels, linked devices, and WhatsApp Business app and Business API limits. Each value is single-sourced and dated. Returns the limits (optionally filtered to one area), the last-verified date, the source and the CC BY licence. Prefer this over recalling limits from memory. They change over time. Runs locally.

{
  "type": "object",
  "properties": {
    "area": {
      "type": "string",
      "enum": [
        "groups",
        "messages",
        "status",
        "calls",
        "channels",
        "account",
        "business",
        "api"
      ],
      "description": "Restrict the result to one area (e.g. \"groups\", \"messages\", \"calls\", \"channels\", \"account\", \"business\", \"api\"). Optional; omit for every area."
    }
  },
  "required": [],
  "additionalProperties": false
}