Skip to main content
POST
Regenerate Webhook Secret

Overview

Generate a new webhook signing secret. The previous secret is immediately invalidated — webhooks will be signed with the new secret from this point forward.

When to Use

  • Your current webhookSecret has been compromised or exposed
  • Rotating secrets as part of your security policy
  • You’ve lost the secret and need a new one

Response Fields

Migration Strategy

To avoid dropping webhooks during rotation:
1

Regenerate Secret

Call this endpoint to get a new secret
2

Update Your Server

Deploy the new secret to your webhook handler
3

Verify

Send a test webhook with POST /webhooks/test to confirm the new secret validates correctly
The new webhookSecret is shown only once in the response. Store it immediately. The old secret stops working as soon as this endpoint is called.

Authorizations

Authorization
string
header
required

JWT access token obtained from /auth/token

Response

Webhook secret regenerated successfully

success
boolean
Example:

true

status
integer
Example:

200

message
string
data
object
meta
object