Integrations & API

Your ATS stays the starting point

Applications come from your system, the interview runs in Talky, the result goes back. Your system triggers interviews itself and can read the status at any time.

30 minutes · based on your roles and your process

Recruiting APItenant-bound key
offerInterview → { id: "itv_4821", status: "prepared", reviewUrl: "…" } // nobody is contacted startInterview ← { id, channel, confirmedNumber, idempotencyKey } → { status: "queued" } session → { outcome: "interview", transcript, recording, analysis }
Read scopeInterview scopeCall scope separate
Example view

Connections

What you can connect

zvoove

Import applications from a cut-off date with details and CV, use positions as a source for agents, return results.

ATS and HR systems

Connect interview processes and results to your applicant tracking. We clarify availability and data scope for your system.

Calendar

Google Calendar and Outlook for follow-up appointments with personal booking links, confirmations and reminders.

WhatsApp Business and SMS

Interviews and invitations via the WhatsApp Business API, SMS as an additional contact route.

Phone channels

Regional phone numbers for inbound and outbound interviews, selectable per campaign.

REST API and webhooks

For individual connections to your own portals, workflows and reporting.

Recruiting API

Start an interview from your ATS

The API separates the internal work order from the step that makes the phone ring.

  1. Check the assignment

    Your system uses the unique application, the job and an active interview agent of your tenant.

  2. Prepare

    offerInterview returns an ID, status prepared and an internal review link. Nobody is contacted.

  3. Start the call

    The recruiter confirms the current phone number. startInterview receives ID, phone channel and confirmed number.

  4. Read back the result

    queued means: order accepted. Whether someone answered and what was said is in the session and call evidence.

Safeguards

Four safeguards in the API

Key per tenant with its own scopes

Read, interview and call scopes are separate. A read-only key cannot trigger a call.

No duplicate call

A unique idempotency key protects against duplicate execution. After a timeout your system reads back the existing session.

Number must be confirmed

If the phone number has changed since preparation, the start is rejected until the recruiter confirms the current number.

Handover with receipt

A saved report only counts as handed over once the target system has accepted it.

Tenant separation

Jobs, agents, applications and conversations belong to one tenant. Identical names create no link.

Evidence in the right context

Call evidence can only be retrieved in the matching application and job context.

Which system should Talky talk to?

Tell us your ATS. We clarify connection, data scope and setup.

Book a demo