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.

audit_id
Unique ID of an event. Use it to recognize a repeat delivery.
sequence
Order of the event within the organization. KeySigner sends earlier events first.
created_at
Unix timestamp in seconds when KeySigner recorded the event.
operation_id
The shared request ID for the request events below. Organization events such as a support grant can have a null value.

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 typeWhat happened and what to read
operation.createdKeySigner accepted a new request for review.

Payload requester_id, operation_hash

approval.challenge_createdAn approver opened a challenge to submit a decision.

Payload challenge_id, approver_id, authenticator_id

operation.approvedThe decision was approved. A package release reached its required owner count.

Payload approval_id, approver_id, authenticator_id, kind

operation.deniedAn approver denied the request.

Payload approval_id, approver_id, authenticator_id, kind

operation.cancelledAn authorized person cancelled the request.

Payload actor

package.registeredKeySigner registered a package and its owner and quorum settings. This event has a null operation ID.

Payload registry, name, owners, quorum, min_tier

package.release.owner_approvedAn owner approved a release that is still waiting for more owners.

Payload approval_id, approver_id

package.release.attestedKeySigner recorded an attestation for the approved package bytes.

Payload approvers

package.release.published_mismatchThe reported digest of the published bytes differed from the approved digest.

Payload approved_digest, observed_digest

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 typeWhat happened and what to read
signing_policy.draft_changedAn author saved different draft rules. The revision identifies the draft.

Payload actor_id, revision

signing_policy.proposedAn author asked for approval of a saved draft.

Payload actor_id, change_id, revision

signing_policy.signedAn approver signed the proposal. More approvals may still be required.

Payload actor_id, change_id, signing_key_id

signing_policy.rejectedAn approver rejected the proposal. The active rules stay in effect.

Payload actor_id, change_id, signing_key_id

signing_policy.activatedThe 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 actor_id, revision, rules, change_id

Members and devices

Match member records by principal_id, group changes by group_id and enrollment or revocation records by device_id.

Event typeWhat happened and what to read
membership.updatedAn administrator saved a member’s roles and status.

Payload actor_id, principal_id, roles, status, revision

group.changedAn administrator created or updated a group and its roles.

Payload actor_id, group_id, name, roles

group.member_addedAn administrator added a member to a group.

Payload actor_id, group_id, principal_id

group.member_removedAn administrator removed a member from a group.

Payload actor_id, group_id, principal_id

group.deletedAn administrator deleted a group.

Payload actor_id, group_id

enrollment.challenge_createdA person started enrolling a device and received a challenge.

Payload enrollment_id, device_id, principal_id

device.enrolledThe device completed enrollment.

Payload device_id, principal_id, assurance_refs

device.revokedAn administrator revoked the enrolled device.

Payload actor_id, principal_id, device_id

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 typeWhat happened and what to read
support.grantedAn authorized person gave KeySigner support time-limited diagnostic access.

Payload actor_id, grant_id, expires_at, reason

support.viewedKeySigner support read diagnostics using an active grant.

Payload grant_id

support.revokedAn authorized person ended access on the matching grant.

Payload actor_id, grant_id

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"
        ]
      }
    }
  ]
}

Download example JSON

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.

Revision 1 · Activated directly
An author saved a rule requiring one eligible key. The activation shows the complete active rules. It has no change_id.
Revision 2 · Approved and activated
An author proposed requiring two keys. The first approval left the original rule active. The second approval was followed by an activation with the same change_id.
Revision 3 · Rejected
An approver rejected a proposal to return to one key. The proposal and rejection share a change_id. Revision 2 stayed active.

Download signing rule events

Compare the most recent activation with Active requirements in the workspace. To run a change yourself, reuse a signing rule in a test workspace.