Kini AI (Beta)

What it does

A candidate finds a job on your job board and applies right there — no redirect to the employer's website.

1. You tell us which job it is (the link to the employer's job ad).
2. We read the employer's application form and give you its fields.
3. You show those fields on your site. The candidate fills them in.
4. You send us the application. We deliver it to the employer.

You do not need to set anything up with the employer. No ATS connection, no employer onboarding.

Two ways to start

However a job reaches us, everything after that works the same way: you fetch the form fields, show them on your site, and send us the application.

Before you start

You need an API key from the Kini App. Send it with every request — see Authentication. You do not need the Company-Id header for Kini AI.

curl 'https://api.getkini.com/jobs/form_fields/?apply_url=https%3A%2F%2Fjobs.example.de%2Fstelle%2F2026-061' \
  --header 'Authorization: Bearer YOUR_API_KEY'

How it works

Step 1: Send us the job link

Only needed on the API path.

curl -X POST 'https://api.getkini.com/jobs/form_fields/' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "apply_url": "https://jobs.example.de/stelle/2026-061",
    "partner_job_id": "your-job-123"
  }'

{
  "apply_url": "https://jobs.example.de/stelle/2026-061",
  "status": "processing"
}

We answer with 202 Accepted and start reading the employer's form. This usually takes a few seconds, sometimes a few minutes.

• Send it when the job is published on your board, not when a candidate clicks "apply". Then the form is ready in time.
• Sending the same link twice is fine. Nothing is duplicated.

Step 2: Get the form fields

curl 'https://api.getkini.com/jobs/form_fields/?apply_url=https%3A%2F%2Fjobs.example.de%2Fstelle%2F2026-061' \
  --header 'Authorization: Bearer YOUR_API_KEY'

{
  "job_id": 48211,
  "status": "ready",
  "apply_url": "https://jobs.example.de/stelle/2026-061",
  "updated_at": "2026-09-22T07:10:00Z",
  "application_form_fields": [
    { "id": "anrede", "label": "Anrede", "type": "select", "required": true,
      "options": [ { "value": "Frau", "label": "Frau" }, { "value": "Herr", "label": "Herr" }, { "value": "Divers", "label": "Divers" } ] },
    { "id": "vorname", "label": "Vorname", "type": "text", "required": true },
    { "id": "email", "label": "E-Mail", "type": "email", "required": true },
    { "id": "lebenslauf", "label": "Lebenslauf", "type": "file", "required": true,
      "accept": ["pdf"], "max_size_mb": 2 },
    { "id": "datenschutz_hinweis", "type": "info",
      "text": "Es gelten unsere <a href="https://www.example.de/datenschutz/">Datenschutzhinweise</a>." },
    { "id": "datenschutz", "label": "Ich stimme der Verarbeitung meiner Daten zu.", "type": "consent",
      "subtype": "application", "required": true }
  ]
}

What status means:

not_supported applies to the employer, not the single job: if we can't handle one of an employer's jobs, we can't handle the others either. This is usually because the employer's website blocks automated applications.

What each field type means, and how to show it: Form Fields.

Step 3: Show the form

Show the fields in the given order, with the employer's labels. Four rules:

1. Show privacy text as it is. Show every info field unchanged, with its links. This is usually the employer's privacy notice.
2. Never tick consent. The candidate must tick consent boxes themselves. We never tick them either.
3. Mark required fields. Don't let the candidate send the form without them.
4. Only offer the given options. For choice fields, show exactly the options we give you.

Step 4: Send the application

Use the normal POST /applications/ endpoint.

{
  "job": 48211,
  "partner_application_id": "your-application-456",
  "candidate": {
    "first_name": "Maria",
    "last_name": "Schneider",
    "email": "maria.schneider@example.com"
  },
  "screening_questions": [
    { "id": "anrede", "answer": "Frau" },
    { "id": "vorname", "answer": "Maria" },
    { "id": "email", "answer": "maria.schneider@example.com" },
    { "id": "datenschutz", "answer": true }
  ],
  "attachments": [
    { "id": "lebenslauf", "name": "lebenslauf.pdf", "content_type": "application/pdf", "data": "JVBERi0xLjQK..." }
  ]
}

{
  "id": 8813204,
  "job": 48211,
  "partner_application_id": "your-application-456",
  "sync_status": "NOTSENT"
}

That's it. We deliver the application to the employer in the background.

Checking the status

Choose what suits you — you can use all three:

When something goes wrong

Questions? Write to tech@getkini.com.