ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
Product Release

Meta WhatsApp Cloud API fully integrated into the standard library

The platform's standard library covers the Meta WhatsApp Cloud API across all interaction directions: send template messages, upload media blobs, receive and parse inbound webhook events, and deserialize template components — all from server-side JavaScript or Python.

WhatsApp Cloud API support shipped incrementally and is now complete: outbound messaging, media upload, inbound webhook parsing, and message template component handling are all available through the Ax.cloud namespace. The client uses the same credential-resolution chain and permission-perimeter model as the other cloud-provider clients.

Outbound messaging and templates

  • First-class cloud provider registration. WhatsApp is registered alongside existing SMS, email, and push providers, so credentials and routing use the same platform credential store.
  • Template component deserialization. Header, body, button, and carousel components in template payloads deserialize into typed objects on the calling side, so scripts inspect or modify components without parsing raw JSON.

Media upload

  • JDBC blob and JavaScript blob inputs. The uploadMedia method accepts both a JDBC Blob and a JavaScript Blob, so scripts pipe database-stored documents directly to WhatsApp without staging on the filesystem.
  • Media ID returned. The method returns the WhatsApp media ID for storage and reference in subsequent messages.

Inbound webhook handling

  • Full typed webhook model. Text, image, audio, video, document, sticker, location, contacts, reaction, and interactive-reply message types all deserialize into a typed model; delivery, read, and failed statuses arrive as structured events with conversation and pricing metadata.

A server-side workflow that triggers a WhatsApp notification on a business event requires no external relay or middleware layer. The role model governs which scripts can invoke the client; underlying credentials are not reachable by a script that lacks the corresponding permission.

← All posts