March 2026

March 28, 2026

Analysis PDF in API & Webhooks: The candidate analysis PDF report is now available as a Base64-encoded string via a dedicated endpoint and in webhooks.
- GET /interviews/:id/analysis-pdf — New endpoint that returns the Base64-encoded PDF report of the candidate analysis. Separated from the main interview resource to keep GET /interviews/:id responses lightweight.
- analysis.completed webhook — Payload now includes analysisPdfBase64 alongside the existing analysis data. If PDF generation fails, the field is omitted and the webhook is delivered normally with the rest of the data.
- Enables clients to download the PDF report on demand or receive it automatically via webhooks.

Anonymized CV Text in API: Candidates now support an optional cvText field for plain text CV input.
- When provided via POST /candidates or PATCH /candidates/{id}, the text is automatically anonymized to remove personally identifiable information (PII).
- The anonymized version is stored and exposed in the anonymizedCvText field in API responses (GET /candidates, GET /candidates/{id}, etc.).
- This feature enables seamless integration for ATS systems that store CVs as plain text while ensuring data privacy for AI-driven analysis.

Interview Transcripts in API & Webhooks: Call attempt transcripts are now exposed in the public API and the analysis.completed webhook.
- GET /interviews/:id — Each callAttempt object now includes a transcript array of chronologically-ordered segments. Every segment contains the speaker (AI or HUMAN), the transcribed text, startTime / endTime (seconds from recording start), and the detected language. Interviews with multiple call attempts each carry their own isolated transcript, preventing segment-order ambiguity.
- analysis.completed webhook — The specific call attempt that triggered the webhook now includes its transcript directly on the call attempt object. Other call attempts in the payload have their transcript omitted to keep the payload focused.
- A new PublicTranscriptSegmentDto schema has been added to the OpenAPI spec documenting the structure of each segment.

Candidate Gender Field: Added an optional gender field ("male" / "female") to the Candidate resource. When set, it is used as the primary source for gender-aware addressing in interviews (e.g., Slovak/Czech formal titles like “pán”/“pani”). If not provided, gender is automatically detected from the candidate’s name. The field can be set during creation, updated later, or cleared by setting it to null to revert to auto-detection. Available on POST /candidates, PATCH /candidates/{id}, and GET /candidates/{id} endpoints.