聆悟 logoLingwu
Creators

Developer API

Programmatic access to interviews, questions, sessions, and candidates

The Lingwu Developer API lets you create and manage AI interviews without using the web UI. Use it for ATS integrations, batch provisioning, or custom hiring workflows.

API keys

Create organization-scoped keys under Settings → API Keys. Each key is prefixed with dlv_ and only works for projects your account can access.

Base URL & authentication

All endpoints live under /api/v1 on your deployment origin (for example https://www.example.com/api/v1).

Authorization: Bearer dlv_your_key_here
Content-Type: application/json

OpenAPI specification: /api/v1/openapi.json

Typical workflow

  1. POST /interviews — create an interview template
  2. POST /interviews/{id}/questions — add questions
  3. POST /interviews/{id}/publish — publish and get a shareable slug
  4. Share the candidate link; candidates complete sessions
  5. GET /interviews/{id}/sessions — list sessions
  6. GET /sessions/{id} — fetch transcript and insights

Endpoints

  • Interviews — GET/POST /interviews, GET/PATCH/DELETE /interviews/{id}
  • Questions — GET/POST /interviews/{id}/questions, PATCH/DELETE /questions/{id}
  • Candidates — GET/POST /interviews/{id}/candidates
  • Sessions — GET /interviews/{id}/sessions, GET /sessions/{id}
  • Usage — GET /usage (organization snapshot for the key)

Errors & limits

Errors return JSON with an error.code and error.message (for example UNAUTHORIZED, NOT_FOUND, RATE_LIMITED). Keys are rate-limited per key; use pagination cursors on list endpoints where documented in OpenAPI.