Rotate a subscription's signing secret

POST
/hooks/subscriptions/{subscriptionId}/secret

Takes effect immediately and with no overlap window: the next attempt of every delivery, including one already queued, is signed with the new secret. Deploy it to your receiver first.

Authorization

apiKey
Authorization<token>

API key as Bearer token: Authorization: Bearer

In: header

Path Parameters

subscriptionId*string

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://terac.com/api/external/v2/hooks/subscriptions/string/secret" \  -H "Content-Type: application/json" \  -d '{}'
{
  "secret": "string"
}
{
  "code": "BAD_REQUEST",
  "message": "Invalid input data",
  "issues": []
}
{
  "code": "UNAUTHORIZED",
  "message": "Authorization not provided",
  "issues": []
}
{
  "code": "FORBIDDEN",
  "message": "Insufficient access",
  "issues": []
}
{
  "code": "NOT_FOUND",
  "message": "Not found",
  "issues": []
}
{
  "code": "INTERNAL_SERVER_ERROR",
  "message": "Internal server error",
  "issues": []
}

Read a subscription's signing secret GET

For recovering a secret you no longer have. Rotate instead if you believe it leaked, since reading it does not invalidate anything.

List webhook deliveries GET

One row per delivery, updated in place across retries, so id is the X-Event-ID your endpoint saw and attempt_count is how many tries it took. Confirmation pings are not logged here.