# Replace example resource IDs and ownerId with values from your workspace.
: "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}"
curl --request POST \
--url 'https://api.migration.powerdialer.ai/api/public/v2/webhooks/00000000-0000-4000-8000-000000000001/verify' \
--header "Authorization: Bearer $POWERDIALER_API_KEY"{
"verified": true,
"active": true
}{
"error": {
"code": "invalid_api_key",
"message": "API key is invalid, expired or revoked",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}Verify a webhook receiver
Prove that the configured receiver can authenticate and acknowledge PowerDialer requests, then enable the subscription. Requires webhooks:manage and the owning credential. Configure the signing secret in your receiver before calling this endpoint; no request body is needed.
PowerDialer sends a signed JSON challenge of type webhook.verification. Verify PowerDialer-Signature against the raw bytes and return a 2xx JSON response echoing the identical challenge within 15 seconds. A successful response here is {verified:true,active:true}. HTTPS public destinations are required; redirects are not followed.
422 verification_failed means the receiver did not return the expected successful challenge response. Correct the handler before explicitly trying again. 409 configuration_changed means configuration changed during verification; verify the latest settings. 400 unsafe_receiver requires a public destination; DNS failures or timeouts can return 503. This operation has no idempotency receipt and should not be automatically retried after an uncertain response.
# Replace example resource IDs and ownerId with values from your workspace.
: "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}"
curl --request POST \
--url 'https://api.migration.powerdialer.ai/api/public/v2/webhooks/00000000-0000-4000-8000-000000000001/verify' \
--header "Authorization: Bearer $POWERDIALER_API_KEY"{
"verified": true,
"active": true
}{
"error": {
"code": "invalid_api_key",
"message": "API key is invalid, expired or revoked",
"requestId": "00000000-0000-4000-8000-000000000004"
}
}Authorizations
Issued in Developers. Workspace/owner/scopes come from credential, never acting-user headers. API keys cannot manage API credentials.
Path Parameters
Subscription UUID returned by registration or listing. It must belong to the credential making this request.