---
title: "Get Audit Log JSON Web Keys"
url: "https://nov18-dev.movespot.fyi/apis/konnect-audit-log-settings-dev-3/versions/53c2c1ad-759f-4471-87e5-bbf9b44f4fd7/operations/get-audit-log-jwks"
---

> Full API specification: https://nov18-dev.movespot.fyi/apis/konnect-audit-log-settings-dev-3/versions/53c2c1ad-759f-4471-87e5-bbf9b44f4fd7.md

# Get Audit Log JSON Web Keys

`GET` `/audit-log-webhook/jwks.json`

Operation ID: `get-audit-log-jwks`

Returns the public keys used to sign audit log entries in order to verify the validity of audit log entries.

## Responses

- `200` - Get response for the audit log JSON Web Keys

## OpenAPI definition

```yaml
openapi: 3.0.2
info:
  title: Konnect Audit Log Settings
  version: 3.0.5
servers:
  - url: https://us.api.konghq.com/v3
    description: United-States Production region
  - url: https://eu.api.konghq.com/v3
    description: Europe Production region
  - url: https://au.api.konghq.com/v3
    description: Australia Production region
  - url: https://me.api.konghq.com/v3
    description: Middle-East Production region
  - url: https://in.api.konghq.com/v3
    description: India Production region
  - url: https://sg.api.konghq.com/v3
    description: Singapore Production region
paths:
  /audit-log-webhook/jwks.json:
    get:
      operationId: get-audit-log-jwks
      summary: Get Audit Log JSON Web Keys
      description: Returns the public keys used to sign audit log entries in order to
        verify the validity of audit log entries.
      responses:
        "200":
          $ref: "#/components/responses/JWKS"
      tags:
        - Audit Logs
security:
  - personalAccessToken: []
  - systemAccountAccessToken: []
components:
  responses:
    JWKS:
      description: Get response for the audit log JSON Web Keys
      content:
        application/json:
          schema:
            type: object
            properties:
              keys:
                type: array
                items:
                  $ref: "#/components/schemas/JWK"
            required:
              - keys
          examples:
            JWKS:
              $ref: "#/components/examples/JWKS"
  schemas:
    JWK:
      description: An individual JSON Web Key.
      type: object
      properties:
        kty:
          description: The algorithm family of the key.
          type: string
        alg:
          description: The algorithm intended for use with the key.
          type: string
        kid:
          description: The unique ID of the key.
          type: string
        crv:
          description: The cryptographic curve used with the key.
          type: string
        x:
          description: The x coordinate for the Elliptic Curve point.
          type: string
      example:
        kty: OKP
        alg: EdDSA
        kid: 3f60bc4376c937154f3c004ebd180433ac0d03e6
        crv: Ed25519
        x: XWxGtApfcqmKI7p0OKnF5JSEWMVoLsytFXLEP7xZ_l8
      required:
        - kty
        - alg
        - kid
        - crv
        - x
      title: JWK
  examples:
    JWKS:
      value:
        keys:
          - kty: OKP
            alg: EdDSA
            kid: 3f60bc4376c937154f3c004ebd180433ac0d03e6
            crv: Ed25519
            x: XWxGtApfcqmKI7p0OKnF5JSEWMVoLsytFXLEP7xZ_l8
  securitySchemes:
    personalAccessToken:
      type: http
      scheme: bearer
      bearerFormat: Token
      description: >
        The personal access token is meant to be used as an alternative to
        basic-auth when accessing Konnect via APIs.

        You can generate a Personal Access Token (PAT) from the [personal access
        token page](https://cloud.konghq.com/global/account/tokens/) in the
        Konnect dashboard.

        The PAT token must be passed in the header of a request, for example:

        `curl -X GET 'https://global.api.konghq.com/v2/users/' --header
        'Authorization: Bearer kpat_xgfT...'`
    systemAccountAccessToken:
      type: http
      scheme: bearer
      bearerFormat: Token
      description: >
        The system account access token is meant for automations and
        integrations that are not directly associated with a human identity.

        You can generate a system account Access Token by creating a system
        account and then obtaining a system account access token for that
        account.

        The access token must be passed in the header of a request, for example:

        `curl -X GET 'https://global.api.konghq.com/v2/users/' --header
        'Authorization: Bearer spat_i2Ej...'`
```
