> 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/api-keys.md). # API Keys API Keys provide secure access to the WhatsApp Business API on behalf of clients. Partners can generate API Keys only if they have the required permissions for the relevant number or channel. ### Partner Permissions Overview Permission to generate API Keys is granted automatically during onboarding. * **Partner Payment**: Partners can manage channels by default. * **Direct Payment**: Clients can revoke or re-grant access at any time via their Client Hub Settings. ### Generating API Keys Partners can verify if they have permission to generate an API Key for a client's channel through the [Partner API](/partner/partner-api/api-reference/client-management.md#get-api-v2-partners-partner_id-clients-client_id-shared_client_numbers). Partners can generate keys in the following ways: #### Using the Partner API Partners can create an API Key programmatically for a specific channel using this [endpoint](/partner/partner-api/api-reference/channel-management.md#post-api-v2-partners-partner_id-channels-channel_id-api_keys). #### Using the Partner Hub 1. Go to the channel details. 2. In the API Settings, click on the icon to create a new API Key.
If permission is missing, the button will be hidden. *** #### Direct Payment Channels Permissions are shared by default during onboarding.\ \ Clients can navigate to [Client Hub](https://app.360dialog.com/), select the channel, go to the "API settings" section, and change the preference in "Partner access":\ \ ![](https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2FmdbGxEmTxQHsFIGuj3jQ%2Fimage.png?alt=media\&token=097d1dc5-09a5-470f-be59-fa6ccebfab74) --- # 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/partner-hub/api-keys.md?ask=&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.