Customers requirement changed - Coinbase Developer Documentation

Authorizations

X-Webhook-Signature

string

header

required

HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.

Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.

Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.

X-Hook0-Signature is deprecated and will eventually be removed. Use X-Webhook-Signature going forward. Both headers are sent with identical values and use the same verification algorithm and webhook secret.

This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.

Headers

X-Webhook-Signature

string

required

HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.

Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.

Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.

This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.

X-Hook0-Signature

string

required

HMAC-SHA256 signature supplied on every webhook delivery. The signature is computed from the raw request body using the webhook secret supplied during creation of the webhook subscription.

Webhook receivers can cryptographically verify this header before processing the event to ensure the authenticity of the webhook delivery.

Refer to the verify signatures documentation to learn details about the full payload and the exact verification algorithm.

This scheme applies to webhook delivery (outbound POSTs from CDP to your endpoint), not to inbound CDP API requests.

Body

application/json

The customers.requirement.changed webhook event payload.

Common envelope fields included in every Customers webhook event payload.

eventId

string<uuid>

required

Unique identifier for this logical webhook event. Webhooks are delivered at least once, so your endpoint may receive duplicate deliveries for the same event. Use this eventId as the idempotency/deduplication key.

Example:

"3a7f8b2e-1c4d-4e9a-b5f6-d8a2c0e7f194"

eventType

enum<string>

required

The type of webhook event.

Available options:

customers.requirement.changed

Example:

"customers.requirement.changed"

timestamp

string<date-time>

required

The UTC ISO 8601 timestamp at which the underlying state change occurred, not the time at which this webhook was delivered.

Example:

"2026-04-01T12:00:02Z"

data

object

required

Payload body for the customers.requirement.changed event. Emitted when the status of one or more requirements changes. Several requirements may change in a single event, with each change represented by a distinct entry in the requirements array.

Show child attributes

Example:

{
  "customerId": "customer_38d54acb-0868-431c-a88e-1ffcb62655eb",
  "requirements": [
    {
      "field": "fullSsn",
      "status": "rejected",
      "impact": ["tradeCrypto"]
    },
    { "field": "ssnLast4", "status": "cleared" }
  ]
}

Response

Webhook received and processed successfully.