---
schema_version: "1"
id: 2dc58739683f487f7c1423f266f564f18d1f4a4ee0949ddd3b659eb6d4641bc0
title: Webhook Data Action Targets in Data 360
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-int/references/webhook-data-action-targets/c360a-api-webhook-data-action-targets-in-customer-data-platform.md
canonical_url: https://developer.salesforce.com/docs/data/data-cloud-int/references/webhook-data-action-targets/c360a-api-webhook-data-action-targets-in-customer-data-platform.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: f637decdccad17016cbdad7f3043f67ad6881b37b0a2c2dafc75a4037c72f397
products:
  - Data 360 Integration Guide
  - Data 360 Developer Documentation
---
# Webhook Data Action Targets in Data 360

Send a Data 360 data action event to a webhook target and protect the message integrity with a Salesforce-generated secret key. A webhook is a type of HTTP request that’s triggered by an event in a source system and sent to a destination system with a payload. A webhook is event-driven rather than request-driven. Webhooks are sent automatically when an event is triggered in the source system. The secret key based signature validates the payload requests sent from Salesforce.

A webhook transports HTTP payload with events in the format of [DataObjectDataChgEvent](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/sforce_api_objects_dataobjectdatachgevent.htm).

```nolang
{
"creationDateTime": "DateTime: Payload creation time at the service calling webhook",
"count": "Number: Count of events in this payload",
"schemas": [ { "schemaId": "Action Name of schema", schema : "Schema of Event Payload in Action" } ], //Array of Schemas for different event payload
"events": [Array of DataObjectDataChgEvent Events],
}
```

- [**Generate a Secret Key for Signature Validation**](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_generate_secret_key_for_signature_validation.htm)

  To protect a webhook system from malicious attacks, generate a secret key for validation. If you don't generate a secret key, targets don't receive a payload, and calls are marked with Signing Key Not Found. In Data 360, data actions use the HMACSHA256 signature algorithm.

- [**Regenerate a Secret Key**](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_regenerate_secret_key.htm)

  We recommend regenerating the secret key used in your webhook system at least every 12 months. After you regenerate a secret key, it takes up to 15 minutes to be effective. Until the new key is configured for use, validations at the webhook target fail.

- [**Payload Signature**](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_payload_signature.htm)

  Payload-based signature validates the payload requests sent to your webhook system from Salesforce.

- [**Validating the Signature**](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_validating_the_signature.htm)

  To validate the signature, you can use this sample Java code. Make sure to perform JSON escaping on the payload received at the target.

**See Also**

- [_Salesforce Developers Blog_: Unleashing the Power of Data Actions Using a Webhook as a Target](https://developer.salesforce.com/blogs/2024/01/unleashing-the-power-of-data-actions-using-a-webhook-as-a-target)