curl --location 'https://api.synerise.com/automation-endpoint/endpoints/authorized/XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX/trigger' \ --header 'Content-Type: application/json' \ --data-raw '{ "complaint": { "id": "cmp-20240610-001", "customer": { "id": "c123456789", "firstName": "Jane", "lastName": "Smith", "email": "jane.smith@example.com", "phone": "+1234567890" }, "dateReceived": "2024-06-10T09:15:30Z", "orderId": "o987654321", "issueType": "product_defect", "description": "The wireless headphones stopped working after two days of use.", "priority": "high", "status": "new", "attachments": [ { "fileName": "photo_of_defect.jpg", "fileUrl": "https://example.com/uploads/photo_of_defect.jpg" } ] }, "source": "customer_support_portal" }'

curl --location 'https://api.synerise.com/automation-endpoint/endpoints/authorized/XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX/trigger' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer {JWT}' \ --data-raw '{ "complaint": { "id": "cmp-20240610-001", "customer": { "id": "c123456789", "firstName": "Jane", "lastName": "Smith", "email": "jane.smith@example.com", "phone": "+1234567890" }, "dateReceived": "2024-06-10T09:15:30Z", "orderId": "o987654321", "issueType": "product_defect", "description": "The wireless headphones stopped working after two days of use.", "priority": "high", "status": "new", "attachments": [ { "fileName": "photo_of_defect.jpg", "fileUrl": "https://example.com/uploads/photo_of_defect.jpg" } ] }, "source": "customer_support_portal" }'

`OK`

This error means that something is wrong with your JSON structure. Check for missing brackets, commas, unescaped quotation marks, and so on.

{
    "error": "Bad Request",
    "message": "Error while deserializing input",
    "status": 400,
    "timestamp": "2025-09-17T10:25:32.050812543Z"
}

This error means that something is wrong with the authorization. Make sure that your token is still valid.

{
    "status": 401,
    "error": "Missing 'Authorization' header or 'access_token' cookie",
    "message": "",
    "timestamp": "2025-09-17 11:13:18Z"
}

This error occurs when the API key selected in the configuration of the incoming integration lacks permissions. For the list of required permissions, see ["Requirements"](#requirements).

{
    "status": 403,
    "error": "Forbidden",
    "message": "",
    "timestamp": "2025-10-03 10:44:52Z"
}

This error occurs when you make a request to a non-published endpoint or the endpoint URL is incorrect. Make sure you copied the entire URL. ``` The requested resource could not be found but may be available again in the future. ```

1. In the **Endpoint** section, click **Define**. 2. In the **URL** field, you can find the endpoint URL which is generated automatically. The endpoint is unique for every integration. 2. From the **API key** dropdown list, select the key which will be used for generating JWT for authentication. You must implement a solution that allows you to authenticate this way.

To generate the JWT, use the [`/uauth/v2/auth/login/profile` endpoint](https://developers.synerise.com/DataManagement/DataManagement.html#operation/profileLogin).

3. Optionally, you can personalize the integration by adding an icon in **Node icon**.

The Endpoint section while creating an incoming integration in Automation Hub

3. Confirm the settings by clicking **Apply**. 4. 1. In the **Incoming data** section, click **Define**. 2. Click **Retrieve data**.

The Retrieve data option in the Incoming data section while creating an incoming integration in Automation Hub

2. Send a POST request to the endpoint defined in the **Endpoint** section. The system waits for the incoming request for 90 seconds. On the basis of received data, the system lists parameters which can be used in the future to filter requests. If the endpoint receives the data, they appear in flattened form. 3. To see the raw JSON, click the

icon. 4. If the received data has the expected structure, confirm by clicking the **Apply** button.

Deduplication is the process that Incoming Integration uses to ensure your workflow only triggers for new information, avoiding duplicates. To prevent duplicated requests, it is possible to select the request parameters from which the deduplication hash will be calculated. 1. To select request parameters, you must first perform instructions described in the "Retrieve data" section in this document. 2. In **Deduplication hash generator** section, click **Define**.

The Deduplication hash generator section while creating an incoming integration in Automation Hub

3. Select up to 5 parameters from which the deduplication hash is to be built. You can use any incoming data from request body and headers. 2. Confirm the settings by clicking **Apply**. Before you start using request deduplication, it's worth reviewing the key concepts: - all deduplication keys are stored for the 7 days. It means that Synerise deduplicates requests with the same deduplication hash for a period of only 7 days from the last sent request. - if a duplicated request is sent, Synerise will return `204` HTTP status code. - for non-duplicated request, Synerise will return `200` HTTP status code. - if you would like to provide your own deduplication hash, you can do so by including it in the request headers. In this case, choose only your header in the **Deduplication hash generator** section in the **Incoming Integration** settings.

1. In the **Endpoint** section, click **Define**. 2. In the **URL** field, you can find the endpoint URL which is generated automatically. The endpoint is unique for every integration. 3. Optionally, you can personalize the integration by adding an icon in **Node icon**.

3. Confirm the settings by clicking **Apply**. 3. 1. In the **Incoming data** section, click **Define**. 2. Click **Retrieve data**.

icon. 4. If the received data has the expected structure, confirm by clicking the **Apply** button.

The full instructions are available in [Webhooks from Meta](/docs/automation/integration/webhook-from-meta).