{"id":2966,"date":"2026-09-16T11:16:53","date_gmt":"2026-09-16T05:46:53","guid":{"rendered":"https:\/\/www.smsgatewaycenter.com\/blog\/?p=2966"},"modified":"2026-09-16T11:16:56","modified_gmt":"2026-09-16T05:46:56","slug":"whatsapp-business-api-wire-contract","status":"publish","type":"post","link":"https:\/\/www.smsgatewaycenter.com\/blog\/whatsapp-business-api-wire-contract\/","title":{"rendered":"WhatsApp Business API Wire Contract: Ten Endpoints, Two Base Paths, Five Envelopes"},"content":{"rendered":"\n

A field-level reference to the WhatsApp Business API on SMSGatewayCenter. Ten operations across two base paths, five distinct response envelopes, the media and template lifecycles, the delivery row compared against SMS, RCS and Telegram, and the parsing traps that silently corrupt identifiers.<\/p>\n\n\n\n

\"Four<\/a>
Four outbound channels, four different wire contracts, one platform.<\/figcaption><\/figure>\n\n\n\n

<\/p>\n\n\n\n

Table of Contents<\/h1>\n\n\n\n
    \n
  1. The Short Answer<\/a><\/li>\n\n\n\n
  2. TL;DR<\/a><\/li>\n\n\n\n
  3. Two Base Paths, One Product<\/a><\/li>\n\n\n\n
  4. The Ten Operation Reference<\/a><\/li>\n\n\n\n
  5. The Send Contract and Why It Is the Outlier<\/a><\/li>\n\n\n\n
  6. Five Response Envelopes in One Family<\/a><\/li>\n\n\n\n
  7. The Success Code Tabulation<\/a><\/li>\n\n\n\n
  8. The Error Payload That Changes Type<\/a><\/li>\n\n\n\n
  9. The Media Lifecycle, Start to Finish<\/a><\/li>\n\n\n\n
  10. Template Management End to End<\/a><\/li>\n\n\n\n
  11. Two Approval States, Not One<\/a><\/li>\n\n\n\n
  12. The Delivery Row Compared Four Ways<\/a><\/li>\n\n\n\n
  13. The Nineteen Digit Number That Breaks JavaScript<\/a><\/li>\n\n\n\n
  14. The Inbox, and What It Costs You<\/a><\/li>\n\n\n\n
  15. Analytics and the Right Denominator<\/a><\/li>\n\n\n\n
  16. Your First Send in Six Steps<\/a><\/li>\n\n\n\n
  17. Four Languages, Four Traps<\/a><\/li>\n\n\n\n
  18. Ten Mistakes That Cost Real Money<\/a><\/li>\n\n\n\n
  19. Choosing WhatsApp Over SMS, RCS or Telegram<\/a><\/li>\n\n\n\n
  20. The Production Checklist<\/a><\/li>\n\n\n\n
  21. Unspecified Behaviour and How to Code Around It<\/a><\/li>\n\n\n\n
  22. FAQs<\/a><\/li>\n<\/ol>\n\n\n\n

    The Short Answer<\/h2>\n\n\n\n

    The WhatsApp Business API on SMSGatewayCenter is ten operations spread across two API generations, and the single most important thing to know before you write any code is that they do not share a response envelope. The older generation lives on https:\/\/unify.smsgateway.center\/WAApi\/<\/code> and covers four resources: send<\/code>, media<\/code>, template<\/code> and report<\/code>. The newer generation lives on https:\/\/unify.smsgateway.center\/rest\/wa\/v1\/<\/code> and covers inbox<\/code> and analytics<\/code>. Both generations take output=json<\/code>. Both accept the apikey<\/code> request header, which is what you should use, with userid<\/code> sent alongside it every time. Two of the ten operations report success through a field that is not called statusCode<\/code>, or that is an integer rather than a string, so branch on the top level status<\/code> string and nothing else. WAApi\/media<\/code> and WAApi\/template<\/code> are the only genuinely REST-shaped resources on the whole platform: one URL each, with the HTTP method selecting the operation, POST to create, GET to read, DELETE to remove. And the delivery report returns uuId<\/code> as an unquoted nineteen digit JSON number, which loses precision the moment a JavaScript client calls JSON.parse<\/code> on it.<\/p>\n\n\n\n

    TL;DR<\/h2>\n\n\n\n