WhatsApp's URL Architecture: The Distributed GraphQL Mesh

Source: Decompiled WhatsApp Android version 2.26.3.79. All endpoints, operation names, and URL patterns are as observed in the client binary. WhatsApp doesn't use a single GraphQL endpoint. It operates a distributed mesh of specialized GraphQL gateways , each serving a distinct domain: payments, generative AI, Oculus/AR, zero-rating, and core messaging. This federated graph architecture enables independent scaling, regional deployment, and security isolation between domains that have no business touching each other's data. This is a deep-dive into how that mesh is structured, how mutations are routed across it, and what the URL patterns reveal about Meta's broader infrastructure strategy. The Three-Schema Foundation Before getting into endpoints, it helps to understand the schema layer they serve: Schema Owner Purpose whatsapp WhatsApp team Core messaging, AI features, payments, maps whatsapp_mex MEX platform team High-trust: DMA interop, parental controls, passkeys, identity facebook