curl -X POST 'https://api.yativo.com/api/v1/business/webhook/wh-01abc123/regenerate-secret' \
-H 'X-Api-Key: YOUR_API_KEY' \
-H 'X-Api-Secret: YOUR_API_SECRET' \
-H 'Idempotency-Key: regen-secret-001'
const response = await fetch(
`https://api.yativo.com/api/v1/business/webhook/${webhookId}/regenerate-secret`,
{
method: 'POST',
headers: {
'X-Api-Key': process.env.YATIVO_API_KEY,
'X-Api-Secret': process.env.YATIVO_API_SECRET,
'Idempotency-Key': `regen-${Date.now()}`,
},
}
);
const data = await response.json();
// Update your environment with data.data.secret immediately
{
"status": "success",
"status_code": 200,
"message": "Webhook secret regenerated successfully",
"data": {
"webhook_id": "wh-01abc123",
"secret": "whsec_newb2c3d4e5f6...",
"updated_at": "2026-06-01T10:00:00.000000Z"
}
}
Webhooks
Regenerate Webhook Secret
Issue a new signing secret for an existing webhook endpoint
POST
/
business
/
webhook
/
{webhook_id}
/
regenerate-secret
curl -X POST 'https://api.yativo.com/api/v1/business/webhook/wh-01abc123/regenerate-secret' \
-H 'X-Api-Key: YOUR_API_KEY' \
-H 'X-Api-Secret: YOUR_API_SECRET' \
-H 'Idempotency-Key: regen-secret-001'
const response = await fetch(
`https://api.yativo.com/api/v1/business/webhook/${webhookId}/regenerate-secret`,
{
method: 'POST',
headers: {
'X-Api-Key': process.env.YATIVO_API_KEY,
'X-Api-Secret': process.env.YATIVO_API_SECRET,
'Idempotency-Key': `regen-${Date.now()}`,
},
}
);
const data = await response.json();
// Update your environment with data.data.secret immediately
{
"status": "success",
"status_code": 200,
"message": "Webhook secret regenerated successfully",
"data": {
"webhook_id": "wh-01abc123",
"secret": "whsec_newb2c3d4e5f6...",
"updated_at": "2026-06-01T10:00:00.000000Z"
}
}
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.
POST https://api.yativo.com/api/v1/business/webhook/{webhook_id}/regenerate-secret
Requires
Idempotency-Key header. After regeneration, update YATIVO_WEBHOOK_SECRET in your environment immediately — the old secret stops working right away.curl -X POST 'https://api.yativo.com/api/v1/business/webhook/wh-01abc123/regenerate-secret' \
-H 'X-Api-Key: YOUR_API_KEY' \
-H 'X-Api-Secret: YOUR_API_SECRET' \
-H 'Idempotency-Key: regen-secret-001'
const response = await fetch(
`https://api.yativo.com/api/v1/business/webhook/${webhookId}/regenerate-secret`,
{
method: 'POST',
headers: {
'X-Api-Key': process.env.YATIVO_API_KEY,
'X-Api-Secret': process.env.YATIVO_API_SECRET,
'Idempotency-Key': `regen-${Date.now()}`,
},
}
);
const data = await response.json();
// Update your environment with data.data.secret immediately
{
"status": "success",
"status_code": 200,
"message": "Webhook secret regenerated successfully",
"data": {
"webhook_id": "wh-01abc123",
"secret": "whsec_newb2c3d4e5f6...",
"updated_at": "2026-06-01T10:00:00.000000Z"
}
}
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
Your API key (yativo_pk_...) from Developers → API Keys. Send together with X-Api-Secret.
Your API secret (yativo_sk_...), shown once when the key is created.
Headers
A unique string per request to ensure idempotent processing.
Path Parameters
The ID of the webhook whose secret you want to regenerate.

