latestOpenAPI 3.0.32026-08-224982,0272.8 MB
e445c15e5bee
Webhook Keys
Register a webhook signing key
Registers a new webhook signing key for an enterprise. The key can be provided inline via a JWKS payload or referenced via a JWKS URI.
Key ID selection: The keyId (derived from the kid field in the JWK, or supplied explicitly for JWKS URI registrations) must be unique within the enterprise. Once a keyId is used — even if the key is later revoked — it is permanently tombstoned and cannot be reused. Plan for this by choosing a stable, unique keyId from the start (e.g. my-key-v2).
Recommended rotation workflow:
- Register the new key under a new keyId (e.g. my-key-v2).
- Update your service configuration to sign webhooks with the new key.
- Revoke the old key only after you have confirmed the new key is working.
Authorization: Caller must be an admin of the specified enterprise.
post/api/policy/v1/enterprises/{enterpriseId}/webhooks/keys
Path parameters
enterpriseIdstring required
The enterprise ID.
Headers
X-BitGo-OTPstring required
OTP code for verification. Required for webhook key management operations.
Request body
Example request
{
"jwksUri": "https://example.com/.well-known/jwks.json",
"keyId": "my-key-v2",
"keyName": "Production Webhook Key"
}Response
Key successfully registered.
Example response
{
"id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
"keyId": "customer-prod-key-2026",
"algorithm": "EdDSA",
"jwksUri": "https://example.com/.well-known/jwks.json",
"status": "ACTIVE",
"createdDate": "2026-01-12T10:30:00.000Z"
}