> 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/partner-hub/wabas-numbers/details.md).

# Details

The **Details** section provides a comprehensive overview of a specific client integration. 

To access these details, click on any channel in the Numbers list

### API Management

To initiate messaging capabilities, an API key must be generated. If the Partner permission is granted the option to generate a unique API key will be enabled. For security purposes, ensure these keys are stored safely and never shared across multiple implementations.

<figure><img src="/files/kzrLhZktHGoEWo7YYu4Y" alt=""><figcaption></figcaption></figure>

### Client and Billing Overview

#### Account Details

* Client Name – The registered name of the business.
* Client Email – The primary contact email for the account.

#### Billing Information

* Channel Subscription – Displays the current plan. Example: Regular (49 EUR / Month).

### WhatsApp Channel Information

<table><thead><tr><th width="256">Field</th><th>Description</th></tr></thead><tbody><tr><td>ID</td><td>The unique 360dialog internal identifier for the channel.</td></tr><tr><td>Phone number</td><td>The registered WhatsApp phone number.</td></tr><tr><td>WhatsApp Display Name</td><td>The name visible to end-users on WhatsApp.</td></tr><tr><td>Business Messaging Limit</td><td>The current messaging limit (e.g., 250, 2K, 10K, 100K, Unlimited).</td></tr><tr><td>Quality Rating</td><td>The health status of the phone number based on end user feedback.</td></tr><tr><td>Hosting Platform Type</td><td>Indicates whether the channel uses On-Premise or Cloud API hosting.</td></tr><tr><td>WABA Channel External ID</td><td>The unique identifier that corresponds to the Phone Number ID on Meta.</td></tr><tr><td>Partner API Key Permission</td><td>The access level granted to the Partner for this specific channel.</td></tr><tr><td>Data Storage Region</td><td>The geographical location where message data is stored at rest. </td></tr><tr><td>Channel Webhook</td><td>The specific endpoint configured to receive event notifications for this channel.</td></tr></tbody></table>

### WABA Information

<table><thead><tr><th width="260">Field</th><th>Description</th></tr></thead><tbody><tr><td>ID</td><td>The unique 360dialog internal identifier for the channel.</td></tr><tr><td>WABA Name</td><td>The name of WABA within the Meta Business Portfolio.</td></tr><tr><td>WABA Status</td><td>The current status of the WABA..</td></tr><tr><td>WABA Type</td><td>The classification of the account (e.g., Shared or On-behalf-Of)</td></tr><tr><td>Timezone ID</td><td>The timezone of the WABA</td></tr><tr><td>Meta Business Manager ID</td><td>The ID of the Meta Business Portfolio owning the WABA.</td></tr><tr><td>Namespace</td><td>The unique string used for identifying message templates.</td></tr><tr><td>Waba Webhook</td><td>The endpoint where Meta events for all phone numbers under this WABA are sent (e.g., incoming messages, status updates).</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.360dialog.com/partner/partner-hub/wabas-numbers/details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.