Skip to main content
POST
Regenerate the HMAC signing secret for a webhook. Use this after a secret is suspected to be compromised, or as part of a routine secret rotation policy.
Requires Idempotency-Key header. After regeneration, update YATIVO_WEBHOOK_SECRET in your environment immediately — the old secret stops working right away.
The new secret is shown only once — store it securely immediately. The old secret is invalidated as soon as the new one is issued.

Authorizations

X-Api-Key
string
header
required

Your API key (yativo_pk_...) from Developers → API Keys. Send together with X-Api-Secret.

X-Api-Secret
string
header
required

Your API secret (yativo_sk_...), shown once when the key is created.

Headers

Idempotency-Key
string
required

A unique string per request to ensure idempotent processing.

Path Parameters

webhook_id
string
required

The ID of the webhook whose secret you want to regenerate.

Response

200 - application/json

New secret issued

status
string
status_code
integer
message
string
data
object