Source type
Customer.io Source Configuration
Customer.io sources receive reporting and data-out webhooks with timestamped Customer.io signature verification.
Customer.io configuration
Create a Customer.io source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Key values for provider signature. FastHook uses these settings to validate each Customer.io delivery before it enters the routing workflow.
Source TypeCUSTOMER_IO
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsWebhook Signing Key
{
"type": "CUSTOMER_IO",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "CUSTOMER_IO",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Customer.io request contract
FastHook signs v0:timestamp:raw-body with HMAC-SHA256 and compares it to x-cio-signature.
Customer.io headers
Preserve x-cio-signature, x-cio-timestamp when sending Customer.io test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.
x-cio-signatureHMAC-SHA256 hex signature.
x-cio-timestampUnix timestamp used in the signed payload.
Customer.io setup
- Create a Customer.io webhook connection using the FastHook Source URL.
- Paste the webhook signing key into FastHook.
- Route by event or campaign/message identifiers.