get.chat is the technology layer behind 360Dialog Inbox: it adds a REST API, multi-webhook delivery, and an embeddable shared inbox on top of the WhatsApp Business API. It is included with the 360Dialog Premium plan at €99 per number per month, so your team can answer customers in the inbox while your developers connect the same WhatsApp number to your own systems. Every number gets its own Inbox at its own web address.
Key Takeaways
- get.chat is the technology layer powering 360Dialog Inbox, included with the Premium plan at €99 per number per month, alongside the Sendout, Automation and Measurement add-ons, a first support response in under 30 minutes, and business verification in 48 hours.
- Each WhatsApp number sends its events to one main webhook, and get.chat forwards every event to multiple independently configured destinations.[2]
- get.chat gives you a hosted inbox for your team, the Inbox API for your own software, an Inbox MCP server for AI agents, an open-source inbox you can embed or host yourself, and a Partner API for ISVs who provision inboxes for their customers.
- The hosted inbox and the Inbox API share one backend, so a reply, assignment, or tag made in one shows up in the other.
What Problem Does get.chat Solve?
Each WhatsApp phone number sends its inbound messages and status updates to one main webhook URL. 360Dialog can attach additional webhook URLs to a number, and the extra destinations receive a copy once the main one confirms delivery.[9] get.chat sits between the API and the systems that consume its events, receiving the webhook and forwarding every payload to multiple, independently configured endpoints.
Each endpoint receives messages as JSON POST requests in the standard WhatsApp webhook format, and administrators can list, inspect, update, and test webhook targets through the inbox settings (Admin Panel) or the API itself.[10] A support team can operate from the inbox while a CRM integration captures the same conversation data and a chatbot handles automated replies, all on the same WhatsApp number.
If your inbox, CRM, and bot all need the same WhatsApp events, get API access and add get.chat through the Premium plan.
What Are the Core Components of get.chat?
get.chat can be reached in four ways: a hosted web inbox, an MCP server that lets AI agents work the Inbox, a REST API, and an open-source front end you can host yourself.[1] Multi-webhook fan-out runs underneath all of them, and a Partner API covers provisioning for ISVs. Each component is independent: Teams can use the inbox with no direct API calls, or build entirely on the API without the inbox UI. All of them run on the same backend and the same data, so a reply sent through the API appears in the hosted inbox, and a reply typed in the inbox appears in the API.
Hosted Inbox
The hosted inbox is a shared WhatsApp inbox that runs in the browser, with nothing to install. You enable it on your channel in the 360Dialog Hub, and each team member signs in with their own login. Conversations can be assigned to a person, tagged, searched, and resolved, and quick replies cover the answers your team sends every day.[3]
Inbox API
The Inbox API is REST-based and available on every Inbox. It covers sending and receiving messages, managing chats, contacts, tags, assignment, templates, and media. Every Inbox has its own base URL at YOUR_STACK_NAME.inbox.getchat.360dialog.io, runs on its own servers and database, and serves all endpoints under /api/v1/.[4] Authentication starts with your channel’s API key, the secret that identifies your number when you call the WhatsApp API. It is the same key you create in the 360Dialog Hub for the WhatsApp API, sent in the D360-Api-Key header. In production, each service gets its own user and token, sent in an Authorization header.[5] Each Inbox keeps up to 1.5 million messages, removing the oldest first when it is full.
Multi-Webhook Fan-Out
Multi-webhook fan-out lets your CRM, chatbot and team inbox all receive every message from the same WhatsApp number, with no custom middleware in between. Each number has one main webhook. get.chat adds webhook demultiplexing: It receives that webhook and forwards every event to multiple, independently configured per-user endpoints. Webhook management is available in the inbox settings, under WABA Webhooks, or through dedicated API endpoints for listing, inspecting, updating, and testing targets.
Embeddable Inbox UI
The inbox frontend is a React application that ships as a Docker image and can be embedded via iframe.[6] White-labeling is controlled through URL query parameters including chat_only, bg_color, hide_logo, and lng for language selection. The source code is available as an open-source project on GitHub at github.com/get-chat/web-app. Inbox owners manage the business profile, permissions, quick replies, tags, user groups, and webhook targets in the inbox settings, and agents handle conversations in the Web App. Each inbox has a default 4 GB media storage quota.[7]
Partner API
The Partner API lets ISVs and resellers provision and manage Inbox instances programmatically.[12] Each customer’s Inbox is created and administered through API calls.
How Does get.chat Relate to the 360Dialog WhatsApp Business API?
get.chat is an extension layer that sits on top of the 360Dialog WhatsApp Business API. The 360Dialog API handles the official Cloud API connection, phone number registration, template management, and message throughput. get.chat adds the multi-agent inbox, webhook fan-out, and the Inbox API on top of that connection. 360Dialog, as an Official Meta Solution Partner, provides the underlying API infrastructure, and get.chat is the product layer that makes that infrastructure accessible to support teams, sales teams, and developers simultaneously.
Your phone number is registered through 360Dialog’s API infrastructure. When you enable the Inbox add-on on the Premium plan, an Inbox is provisioned on the getchat.360dialog.io subdomain for that number. From that point, the Inbox API, the webhook fan-out, and the Web App are all available through that Inbox, while the underlying Cloud API connection continues to run through 360Dialog. If you already send through the WhatsApp API, the Inbox records every conversation on that number, which gives you a searchable history and a human fallback with nothing extra to build.
If you are still deciding whether the hosted inbox, the API, or both fit your team, talk to us about the setup that matches how your team works.
Who Is get.chat Built For?
get.chat serves three audiences: developers who want programmatic control over WhatsApp conversations, support and sales teams who need a shared inbox without building one from scratch, and ISVs or resellers who provision and manage Inbox instances for their customers programmatically.
For developers, the Inbox API means the everyday inbox actions (sending messages, reading history, assigning chats, tagging, uploading media) are available as REST calls. That makes it possible to connect WhatsApp to any internal system through standard HTTP requests. If your team is already building a sales pipeline without a CRM, the API lets you automate lead tagging and conversation routing programmatically.
For support and sales teams, the Web App provides a shared inbox where multiple agents handle conversations on the same WhatsApp number. Tags allow grouping contacts by status, transaction type, or lead stage. Quick replies speed up answers while the customer service window is open, which is 24 hours from the customer’s last message.[11] When a customer writes from a Click to WhatsApp ad and you reply within that window, Meta opens a free entry point window in which it does not charge for marketing, utility, authentication or service messages.[13] Teams already managing WhatsApp as a team with a shared inbox will find that get.chat provides the underlying technology for those capabilities.
For ISVs and resellers, the Partner API lets partners provision and manage Inbox instances programmatically.
What Does get.chat Cost?
get.chat’s capabilities are included with the 360Dialog Premium plan at €99 per number per month.[8] The Inbox is available to 360Dialog direct clients on the Premium plan at no extra charge. The Premium plan bundles the Inbox add-on alongside Sendout, Automation, and Measurement add-ons. The Regular plan at €49 per number per month does not include the Inbox add-on. The Scale plan at €500 per number per month includes everything in Premium with throughput of up to 1,000 messages per second. To see how this compares with WATI, Respond.io and Trengo, read our team inbox comparison.
The Inbox requires an active channel on the Premium plan, and you activate it from the 360Dialog dashboard once that channel is live.
get.chat combines direct API access and a managed inbox through a single layer on the 360Dialog platform. For teams that need programmatic control alongside agent-ready conversations on the same WhatsApp number, the necessary components are available through a single plan.
To put get.chat’s shared inbox and Inbox API on your WhatsApp Business number, activate your inbox on the 360Dialog Premium plan.
Frequently Asked Questions
Is get.chat the Same as 360Dialog Inbox?
Yes. get.chat is the technology layer that powers 360Dialog Inbox. The shared inbox, the Inbox API, the multi-webhook fan-out, and the embeddable UI are all get.chat components, delivered as the Inbox add-on within 360Dialog’s Premium plan. The documentation lives in the Inbox section of docs.360dialog.com, and each Inbox runs at its own address on getchat.360dialog.io.
Does get.chat Replace the WhatsApp Business API?
No. get.chat is an extension layer that adds capabilities on top of the existing API connection. The WhatsApp Business API (via 360Dialog’s Cloud API) still handles message sending, template management, and phone number registration. get.chat layers the shared inbox, webhook fan-out, and the Inbox API over that foundation.
Can Multiple Systems Receive WhatsApp Messages From the Same Number?
Yes. 360Dialog can attach several webhook URLs to one number, and get.chat’s multi-webhook fan-out forwards every message and status update to as many endpoints as you configure. Each endpoint operates independently, so your CRM, inbox, and automation platform can all process the same events without custom middleware.
Is the get.chat Inbox Frontend Open Source?
The inbox frontend (the Web App) is an open-source React application available on GitHub at github.com/get-chat/web-app. It ships as a Docker image and can be embedded via iframe with white-labeling options for logo, background color, and language. The backend APIs and infrastructure are hosted by 360Dialog on the getchat.360dialog.io subdomain.
Sources
[1] 360Dialog Documentation, “Inbox Overview.” https://docs.360dialog.com/docs/inbox/overview Accessed September 30, 2026.
[2] 360Dialog Documentation, “Inbox API.” https://docs.360dialog.com/docs/inbox/inbox-api Accessed September 30, 2026.
[3] 360Dialog Documentation, “Working Chats” (Hosted Inbox). https://docs.360dialog.com/docs/inbox/hosted-inbox/working-chats Accessed September 30, 2026.
[4] 360Dialog Documentation, “Making Requests” (Inbox API reference). https://docs.360dialog.com/docs/inbox/inbox-api/reference/making-requests Accessed September 30, 2026.
[5] 360Dialog Documentation, “Authentication” (Inbox API). https://docs.360dialog.com/docs/inbox/inbox-api/authentication Accessed September 30, 2026.
[6] get.chat embedding guide. https://docs.getchat.360dialog.io/guides/2-embedding-the-inbox/. Accessed September 9, 2026.
[7] get.chat Inbox settings reference. https://docs.getchat.360dialog.io/inbox/3-admin-panel/. Accessed September 9, 2026.
[8] 360Dialog pricing. https://360dialog.com/pricing. Accessed September 9, 2026.
[9] 360Dialog Partner Documentation, “Set multiple webhooks for Phone Number.” https://docs.360dialog.com/partner/onboarding/webhook-events-and-setup/set-multiple-webhooks-for-phone-number Accessed September 28, 2026.
[10] 360Dialog Documentation, “Receiving Messages” (Inbox API). https://docs.360dialog.com/docs/inbox/inbox-api/receiving-messages Accessed September 30, 2026.
[11] Meta for Developers, “Service messages.” https://developers.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages Accessed October 23, 2026.
[12] get.chat documentation, “Build on WhatsApp, Without the WhatsApp Business API Headaches.” https://docs.getchat.360dialog.io/ Accessed September 30, 2026.
[13] Meta for Developers, “Pricing on the WhatsApp Business Platform.” https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing Accessed October 23, 2026.
