WhatsApp API integration example

A freelance job post for a baby gear rental service put a rough public price on a real WhatsApp build: about $8,500 for a system that could chat with customers, take payments, and use maps instead of just sending texts. (x.com)(x.com) That price makes more sense once you see what “WhatsApp integration” usually means in practice. Meta’s official WhatsApp Cloud Application Programming Interface runs through the Graph interface, uses bearer tokens for authentication, and sits inside a Business Manager setup with business and phone-number objects to configure before a customer ever gets a message. (developers.facebook.com)(developers.facebook.com) A working commerce bot also needs preapproved message templates for anything proactive, like order updates or payment reminders. Meta’s template interface lets businesses create, fetch, and manage those templates on a WhatsApp Business Account, which turns copywriting and approval into part of the engineering job. (developers.facebook.com)(developers.facebook.com) Even the “chatbot” part is not just one switch. Meta exposes separate conversational automation controls for welcome messages, ice-breaker prompts, and bot commands, so a developer has to design the flow customers see before they type a single question. (developers.facebook.com)(developers.facebook.com) The payment piece usually lives outside WhatsApp itself. Another recent Upwork listing asked for WhatsApp bill sending plus payment-gateway integration, with options like payment links, Hypertext Markup Language invoice pages, or Portable Document Format attachments, which is the kind of stack that turns a chat into a checkout. (upwork.com)(upwork.com) Maps add another layer because location has to connect to business logic. A rental company is not just dropping a pin on a screen; it is checking delivery zones, pickup addresses, travel time, and item availability against a customer’s conversation in real time, which is why a “WhatsApp project” quickly becomes an operations project. (x.com)(x.com) There is also a split between setup work and application work. One Upwork post asked only for official WhatsApp setup, Meta-side configuration, and verification help because the client already had a separate app developer, which shows how onboarding the channel can be its own paid specialty. (upwork.com)(upwork.com) And the meter keeps running after launch. Meta’s own documentation says messages sent from the Cloud Application Programming Interface are billed under the existing pricing model, while one-to-one messages sent from the WhatsApp Business app itself remain free, so the build budget is only the opening cost and not the full cost of operating the bot. (developers.facebook.com)(developers.facebook.com)