KeySigner audit event reference
Look up event types and payload fields for approval requests, package releases, signing rules, team changes, devices and support access.
Fields in every event
A verified webhook body contains an events array. Read each event’s event_type to know which fields to expect in its payload. The webhook can deliver event types beyond this reference.
Requests and releases
Match the request events by operation_id. To check whether a release actually published, verify the package version and build in your registry.
| Event type | What happened and what to read |
|---|---|
operation. | KeySigner accepted a new request for review. Payload |
approval. | An approver opened a challenge to submit a decision. Payload |
operation. | The decision was approved. A package release reached its required owner count. Payload |
operation. | An approver denied the request. Payload |
operation. | An authorized person cancelled the request. Payload |
package. | KeySigner registered a package and its owner and quorum settings. This event has a null operation ID. Payload |
package. | An owner approved a release that is still waiting for more owners. Payload |
package. | KeySigner recorded an attestation for the approved package bytes. Payload |
package. | The reported digest of the published bytes differed from the approved digest. Payload |
Signing rules
Match proposals, decisions and governed activations by change_id. Compare the revision on the draft, proposal and activation. These events have a null operation_id.
| Event type | What happened and what to read |
|---|---|
signing_ | An author saved different draft rules. The revision identifies the draft. Payload |
signing_ | An author asked for approval of a saved draft. Payload |
signing_ | An approver signed the proposal. More approvals may still be required. Payload |
signing_ | An approver rejected the proposal. The active rules stay in effect. Payload |
signing_ | The active rules changed. The actor is the author of the proposal when approvals were required. change_id is present only after a governed change. Payload |
Members and devices
Match member records by principal_id, group changes by group_id and enrollment or revocation records by device_id.
| Event type | What happened and what to read |
|---|---|
membership. | An administrator saved a member’s roles and status. Payload |
group. | An administrator created or updated a group and its roles. Payload |
group. | An administrator added a member to a group. Payload |
group. | An administrator removed a member from a group. Payload |
group. | An administrator deleted a group. Payload |
enrollment. | A person started enrolling a device and received a challenge. Payload |
device. | The device completed enrollment. Payload |
device. | An administrator revoked the enrolled device. Payload |
Support access
Match records for the same grant by grant_id. The expires_at field is a Unix timestamp in seconds. The reason field contains the text entered when the grant was made.
| Event type | What happened and what to read |
|---|---|
support. | An authorized person gave KeySigner support time-limited diagnostic access. Payload |
support. | KeySigner support read diagnostics using an active grant. Payload |
support. | An authorized person ended access on the matching grant. Payload |
Package release example
These two records came from one package release in a test organization. They have the same operation_id and different audit_id values. The second record follows the approval and shows the owners listed in the attestation.
{
"events": [
{
"sequence": 17,
"audit_id": "ce650a54-9b17-41bc-8301-96cc308dfdca",
"event_type": "operation.approved",
"operation_id": "c806c81b-3b8b-4791-9298-f817e46ae00f",
"created_at": 1795001718,
"payload": {
"approval_id": "b8aa079a-5cbf-4eba-8d99-4bcc4d92f788",
"approver_id": "a2a2a2a2-a2a2-4a2a-8a2a-a2a2a2a2a2a2",
"authenticator_id": "31acdcae-2cf1-440d-84e6-d71268b2210a",
"kind": "package.release"
}
},
{
"sequence": 18,
"audit_id": "6b61031c-9bf0-4862-9244-a0d7b68c02cd",
"event_type": "package.release.attested",
"operation_id": "c806c81b-3b8b-4791-9298-f817e46ae00f",
"created_at": 1795001718,
"payload": {
"approvers": [
"a2a2a2a2-a2a2-4a2a-8a2a-a2a2a2a2a2a2",
"bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb"
]
}
}
]
}Signing rule example
These records came from a local test organization running KeySigner API build 323398ba5. They show three revisions of the rule for signing an Ethereum message.
Compare the most recent activation with Active requirements in the workspace. To run a change yourself, reuse a signing rule in a test workspace.