> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/inbox/provisioning-inboxes.md).

# Provisioning Inboxes

This page describes the process for provisioning and removing 360dialog Inboxes for client channels via the Partner API.\
\
\
The WhatsApp Business Platform does not feature a native messaging interface. A 360dialog inbox application can be provisioned for a channel to manage conversations, assign chats to agents, and use quick replies. Read more in the [Inbox overview](https://docs.360dialog.com/docs/inbox/overview) article.&#x20;

<div data-with-frame="true"><figure><img src="https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2FpTAwE42kO2F33XSqkbIq%2FScreenshot%202026-10-23%20at%2012.31.28.png?alt=media&amp;token=a5259236-b833-4f90-abef-eefe2c01171c" alt=""><figcaption><p>360dialog Inbox Interface</p></figcaption></figure></div>

### Prerequisites

Before provisioning an inbox, commercial terms must be established. Reach out to the assigned Account Manager or [360dialog Support](https://docs.360dialog.com/docs/support/get-support) to enable inbox provisioning permissions for the Partner Account.

### How to provision an Inbox

{% stepper %}
{% step %}
To provision an inbox for a channel, execute a `POST` request to the [Channel Products](https://docs.360dialog.com/partner/partner-api/api-reference/channel-products#post-api-v2-partners-partner_id-channels-channel_id-products) endpoint:

```
curl -X POST "https://hub.360dialog.io/api/v2/partners/PARTNER_ID/channels/CHANNEL_ID/products" \
  -H "x-api-key: YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"product": "inbox"}'
```

The API returns an initial provisioning status response:

```
{
  "channel_id": "CHANNEL_ID",
  "product": "inbox",
  "state": "PROVISIONING"
}
```

{% endstep %}

{% step %}
Replace CHANNEL\_ID with the appropriate channel id in the following link:\
\
<https://partner-api.getchat.360dialog.io/inbox?channel\\_id=CHANNEL\\_ID\\>
\
Open the link.&#x20;
{% endstep %}
{% endstepper %}

**Checking Inbox Provisioning Status**

To check the current status of an inbox product on a channel, execute a `GET` request to the [Channel Product Details](https://docs.360dialog.com/partner/partner-api/api-reference/channel-products) endpoint:

```
curl -X GET "https://hub.360dialog.io/api/v2/partners/PARTNER_ID/channels/CHANNEL_ID/products/inbox" \
  -H "x-api-key: YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json"
```

Once provisioning completes, the response reflects the active state:

```
{
  "channel_id": "CHANNEL_ID",
  "instance_url": null,
  "product": "inbox",
  "ready": true,
  "state": "PROVISIONED"
}
```

**Removing an Inbox**

To remove an inbox product from a channel, execute a `DELETE` request to the [Remove Channel Product](https://docs.360dialog.com/partner/partner-api/api-reference/channel-products#delete-api-v2-partners-partner_id-channels-channel_id-products-product) endpoint:

```
curl -X DELETE "https://hub.360dialog.io/api/v2/partners/PARTNER_ID/channels/CHANNEL_ID/products/inbox" \
  -H "x-api-key: YOUR_API_KEY_HERE" \
  -H "Content-Type: application/json"
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.360dialog.com/partner/inbox/provisioning-inboxes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
