Lever Audit Events API

The Audit Events API from Lever — 1 operation(s) for audit events.

Operations 1

GET /audit_events List all audit events in your Lever account, sorted in descending chronological… #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/lever:lever-audit-events-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

lever-audit-events-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Lever Audit Events API
  version: '2026-11-05'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-05: 114 operation(s) read from 3 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Lever has published no machine-readable contract that the pipeline could find. Engine: anthropic.'
  x-evidence-tiers:
    code-example: 86
    documentation: 102
    pages-with-code: 2
    pages-read: 3
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-05'
  x-generator: generate-contract-from-docs.py
  x-engine: anthropic
  x-sources:
  - https://hire.lever.co/developer/updates
  - https://hire.lever.co/developer/deprecated
  - https://hire.lever.co/developer/documentation
  x-cleaned: '2026-11-05: 112 operations kept of 188 generated; 88 example-instance paths folded onto their documented template, 76 dropped because their METHOD+path is not on the documentation or Deprecated page (receiver examples, /oauth/token on auth.lever.co, /j/{jid}, literal-id instances already covered). Then 2 documented operation(s) recovered from the earlier generated contract: GET /opportunities/deleted, POST /postings/{posting}/apply.'
servers:
- url: https://api.lever.co/v1
  description: Production (the root URL for the Lever API web service is https://api.lever.co/v1)
- url: https://api.sandbox.lever.co/v1
  description: Integrator Sandbox (partner program; https://hire.lever.co/developer/partner)
security:
- basic: []
tags:
- name: Audit Events
paths:
  /audit_events:
    get:
      operationId: get_audit_events
      tags:
      - Audit Events
      summary: List all audit events in your Lever account, sorted in descending chronological…
      x-source: https://hire.lever.co/developer/documentation
      parameters:
      - name: type
        in: query
        required: false
        schema:
          type: string
        description: Filter returned events to a single event type
      - name: user_id
        in: query
        required: false
        schema:
          type: string
        description: Filter returned events by the user who performed the action
      - name: target_type
        in: query
        required: false
        schema:
          type: string
        description: Filter returned events to actions on a particular kind of resource
      - name: target_id
        in: query
        required: false
        schema:
          type: string
        description: Filter returned events to actions on a particular resource
      - name: created_at_start
        in: query
        required: false
        schema:
          type: integer
        description: Filter returned events to the ones which occurred at or after a particular time (milliseconds)
      - name: created_at_end
        in: query
        required: false
        schema:
          type: integer
        description: Filter returned events to the ones which occurred at or before a particular time (milliseconds)
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetAuditEventsResponse'
      x-evidence:
        kind: documentation
components:
  schemas:
    GetAuditEventsResponse:
      type: object
      properties:
        id:
          type: string
          description: Audit Event UID
        createdAt:
          type: integer
          description: Time when the event was recorded (milliseconds since Unix epoch)
        type:
          type: string
          description: The tracked action
        user:
          type: object
          description: User who performed the action
        target:
          type: object
          description: The resource the action was performed on
        meta:
          type: object
          description: Additional data about the event
  securitySchemes:
    basic:
      type: http
      scheme: basic