Starts a signing-secret rotation.
POST
/api/notifications/destinations/{id}/secret-rotation/begin
deprecated
Requires: Notifications.Destinations, Notifications.Destinations.Update, merchant scope.
The destination begins signing every delivery with both the current secret and the replacement, emitting two comma-separated `v1=sha256:` entries in `X-WinkPG-Signature` until the rotation is promoted or cancelled. The response carries the replacement secret in plaintext, and is the only place it is ever returned. Confirm the receiver reads every comma-separated entry in the signature header before calling this: a receiver that reads one value rejects every delivery for the length of the overlap, and repeated rejections durably suppress the endpoint.
Example request
Every block below sends the same request. Replace {{BASE_URL}} with the address of the API you are calling and {{API_KEY}} with your own key.
The request body is a BeginWebhookSecretRotationInput. See the Request body section below for its fields.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
id
required |
path | string (uuid) | |
suppressNulls
required |
query | boolean | If true, omit properties with null values. |
Request body
application/json
, required
| Field | Type | Description |
|---|---|---|
incomingSecretKey
required |
string | The replacement secret, or null to have the server generate one. nullable |
This request body has no documented fields.
Responses
200 OK
Body: BeginWebhookSecretRotationResultDto
Each item has these fields.
| Field | Type | Description |
|---|---|---|
incomingSecretKey
required |
string | The replacement secret, in plaintext. Shown to the operator once; never returned again. nullable |
state
required |
all of WebhookSecretRotationStateDto | The destination's rotation state after the operation. |
This response has no documented body fields.
default The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. See the error-code reference in this document's description for the values `error.code` can take.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
429 The request was refused because a rate limit was exceeded. Wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling.
Body: RateLimitProblemDetails
Each item has these fields.
| Field | Type | Description |
|---|---|---|
type
required |
string | The problem type identifier. Always the same value: the failure is the status code itself, so there is no sub-type for a caller to branch on. nullable |
title
required |
string | A short, human-readable summary of the problem type. nullable |
status
required |
integer (int32) | The HTTP status code, repeated in the body as the problem-details format defines. |
detail
required |
string | A human-readable explanation of this occurrence of the problem. nullable |
retryAfterSeconds
required |
integer (int32) | How long to wait before retrying, in whole seconds, carrying the same figure as the `Retry-After` header. Always at least one: a value of zero would invite an immediate retry that is certain to be rejected again. |
This response has no documented body fields.
Errors
A failed request returns the platform error envelope. The
error reference lists every value
error.code can carry and shows the four response shapes.