# Integration

The Integration Settings section contains the core identifiers and endpoints required to manage the connection between 360Dialog, Meta, and a Partner's own infrastructure.

To access these configurations, navigate to **Integration,** [or click here.](https://hub.360dialog.com/dashboard/partner/integration)

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

## Settings

### IDs

* **Partner ID** – A unique, system-generated identifier for the Partner Account. This ID is permanent and cannot be edited or customised.
* **Solution ID** – The Meta Solution ID associated with the partner application. This must be a numeric sequence between 14 and 18 digits in length. A Solution ID is retrieved from the Meta App Dashboard.

### Webhooks and Redirects

* **Partner Webhook URL** - This is the resource to which 360dialog sends real-time event notifications regarding WhatsApp accounts. This URL can be added or edited to point to a preferred listener service.
* **Redirect URL (Integrated Onboarding)** - The resource to which 360dialog redirects clients after they complete a number registration via the Embedded Signup flow. This URL can be updated to manage the post-onboarding user experience.

### Global Configurations

These settings define default behaviours for all WhatsApp numbers registered under the Partner Account.

* **Data Storage Region** - This defines the local storage region for the Meta Cloud API. For example, if the Data Storage Region is set to US, all numbers registered under the account will default to US-based local storage.
* **Legacy Token Authentication** - This option allows authentication using legacy token-based access. For enhanced security, it is recommended to disable this feature and use API key authentication instead.
* **Route Marketing via MM API** - When enabled, this setting routes marketing messages via the MM API where possible. If a message is ineligible for this path, it automatically falls back to the Cloud API to ensure delivery.

### Platform Secret

The platform secret is a new optional security feature, used by 360Dialog to sign webhook events sent to the partner's webhook URL, and by the partner to authenticate Integrated Onboarding requests via [IO Signature](/partner/onboarding/integrated-onboarding/io-signature.md).

* **Platform Secret** - This is a shared secret between 360Dialog and the partner. Once generated, 360Dialog uses the secret to sign the raw webhook body using HMAC-SHA256. The signature is provided in each webhook event's `x-360dialog-signature` header.\
  \
  Partners can validate the request's authenticity by signing the raw request body with the platform secret using HMAC-SHA256, then comparing their signature with the `x-360dialog-signature` header. [See webhook signature validation instructions here.](/partner/onboarding/webhook-events-and-setup/signature-validation.md)\
  \
  See [#generate-platform-secret](#generate-platform-secret "mention") below for instructions on getting/generating a platform secret.
* **IO Signature** - When enabled, the partner must generate an HMAC-SHA512 signature and provide it in the Integrated Onboarding link as a query parameter. All Integrated Onboarding requests without a valid signature are interrupted. [See here for an IO Signature generation example](/partner/onboarding/integrated-onboarding/io-signature.md), and [here for examples of using the generated signature.](/partner/onboarding/integrated-onboarding.md)

## Generate Platform Secret

{% stepper %}
{% step %}

### Navigate to Integration

Navigate to **Integration** in the 360Dialog Hub, [or click here.](https://hub.360dialog.com/dashboard/partner/integration)
{% endstep %}

{% step %}

### Click Generate Platform Secret

Click **Generate Platform Secret** to generate the secret.

{% hint style="info" %}
**Regenerating Platform Secret**

If the platform secret was previously generated, it is possible to regenerate it by clicking **Regenerate Platform Secret.**

**This option may be used if the platform secret has leaked.**

Ensure that **IO Signature** is turned off before regenerating.
{% endhint %}

<div align="left"><figure><img src="/files/iezvaOBXlB5HNp0R7YOT" alt="" width="361"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Enter OTP

An OTP will be sent via e-mail. Enter it to proceed to the next step.

<div align="left"><figure><img src="/files/hFmH2OAVnX0dhovMzob0" alt="" width="479"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Copy Secret

Copy the shown secret.

It is possible to view the secret multiple times by clicking **View secret**.

{% hint style="warning" %}
**Store safely**

Platform secret must be kept secure to benefit from its security advantages.

Store the platform secret in a secure secret manager, or pass it to the server via an environment variable.
{% endhint %}

<div align="left"><figure><img src="/files/BTDHXAaR5OPL6kUCTjg0" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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:

```
GET https://docs.360dialog.com/partner/partner-hub/integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.