Jobs API and Webhooks

Read your published jobs without a key, send applications from your server, and get webhooks when a job changes or an application moves.

Feature Guide
Updated Nov 14, 20267 min readBy Sebastian Streiffert
Who has it
Workspaces that run Bemanning, or Consulting with recruiting on.
Reading jobs
No API key. Anyone can read what your career page already shows.
Applications and webhooks
A workspace admin creates the API key or the webhook under SettingsWorkspace.

Use the jobs API when you build the jobs pages on your own site yourself. If you only want your jobs and an application form on a page, the jobs embed does it with two lines of code.

  1. Read your published jobs, from the browser or your server.
  2. Send each application from your server with a key that can only apply.
  3. Add a webhook to hear when a job changes or an application moves.

List published jobs

One request lists every published job inside its publish dates that is listed on your career page, newest first, up to 200. It needs no key and answers any website, so you can call it from the browser. workspace is your workspace address, as in your career page link.

List jobs
curl "https://api.lumenbase.io/functions/v1/v1-public-jobs?workspace=northwind-staffing"
From the browser
const res = await fetch(
  'https://api.lumenbase.io/functions/v1/v1-public-jobs?workspace=northwind-staffing'
);
const { data } = await res.json();
for (const job of data.posts) console.log(job.title, job.location);
Response (200, shortened)
{
  "success": true,
  "data": {
    "workspace": { "name": "Northwind Staffing", "slug": "northwind-staffing", "logo_url": null },
    "posts": [
      {
        "slug": "truck-driver-gothenburg",
        "title": "Truck driver",
        "location": "Gothenburg",
        "employment_form": "tillsvidare",
        "published_at": "2026-11-10T08:00:00Z",
        "publish_until": "2026-12-01T00:00:00Z",
        "work_location": "onsite",
        "work_schedule": "full_time"
      }
    ]
  },
  "meta": { "request_id": "req_...", "api_version": "1", "timestamp": "2026-11-14T10:00:00.000Z" }
}
FieldWhat it holds
slugThe job's address. Use it to read the job and to apply.
titleThe title as written. Job text is never translated.
locationThe place, or null
employment_formtillsvidare (permanent), visstid (fixed term), timanstalld (hourly), or null
work_locationonsite, hybrid, remote, or null
work_schedulefull_time, part_time, shifts, or null
published_atWhen it was published
publish_untilThe last day, only when the job shows its end date
The list has no descriptions. Answers may be cached for 60 seconds, so a job you publish or close can take a minute to show.

Read one job

Add post with the job's address. The answer has data.post with the list fields plus the description, how many days an application is kept (retention_days), the application deadline, the hiring company's name and logo, and external_apply_url when the job takes applications on another site.

One job
curl "https://api.lumenbase.io/functions/v1/v1-public-jobs?workspace=northwind-staffing&post=truck-driver-gothenburg"

The description is plain text with a small markup: a line starting with # is a heading, a line starting with - is a list item, and **text** is bold. Draw it as text, never as HTML.

Send applications

Applications from your own form go to /v1-public-job-applications with an API key that has only jobs:apply. Send them from your server: the key must never be in a web page. The fields, answers and limits are in REST API, under Send job applications.

Ask the applicant to agree to a consent sentence and send it as consent_text, exactly as they saw it. It is stored with the application. Use retention_days from the job to say how long it is kept.

Hear about changes with webhooks

Add a webhook under SettingsWorkspaceIntegrationsWebhooks and pick the events under Job posts and Applications. These groups show only in workspaces with recruiting.

EventWhen it is sent
job.publishedA job is published, or created as published
job.updatedA published job is saved with a change to its address, title, description, place, dates, deadline, schedule, extent, positions, start date, salary, occupation, municipality, company name, apply link or whether it is listed
job.closedA job is closed
application.receivedAn application arrives, from any source
application.stage_changedAn application moves to another stage, Hired and Declined included

job.updated

changed_fields lists what changed and previous holds the old values. The old description is left out, because it can be long; read the job again for the new one. Saving a job without a change sends nothing, and publishing or closing sends its own event instead.

Body (job.updated, shortened)
{
  "event_type": "job.updated",
  "entity_type": "job",
  "data": {
    "record": {
      "id": "5b2f0c1e-...",
      "slug": "truck-driver-gothenburg",
      "title": "Truck driver, nights",
      "status": "published",
      "location": "Gothenburg",
      "employment_form": "tillsvidare",
      "publish_from": null,
      "publish_until": "2026-12-15T00:00:00Z"
    },
    "changed_fields": ["title", "description", "publish_until"],
    "previous": { "title": "Truck driver", "publish_until": "2026-12-01T00:00:00Z" },
    "source": "database"
  }
}

application.stage_changed

data.record.stage is the new stage and previous.stage the old one. The stages are applied, screening, interview, offer, hired and declined. A declined application carries its decline_reason.

Body (application.stage_changed, shortened)
{
  "event_type": "application.stage_changed",
  "entity_type": "application",
  "data": {
    "record": {
      "id": "9a8b7c6d-...",
      "stage": "interview",
      "decline_reason": null,
      "name": "Sara Ek",
      "candidate_id": "4e5f6a7b-...",
      "contact_id": null,
      "job_slug": "truck-driver-gothenburg",
      "job_title": "Truck driver"
    },
    "changed_fields": ["stage"],
    "previous": { "stage": "screening" },
    "source": "database"
  }
}

Every delivery is signed the same way as the other webhooks. How to check the signature is in REST API, under Get told when records change.

Limits

  • Reading: about 120 requests a minute and 1,200 an hour from one internet address. Cache the list instead of asking on every page view.
  • Up to 200 jobs in the list.
  • Imports, such as the Recman jobs import, send no webhooks for the jobs and applications they bring in.
  • One webhook can pick at most 40 events. Picking none means every event.

Troubleshooting

404 No career site for this workspace

  1. Check workspace: it is the address in your career page link, not the workspace name.
  2. Check that the workspace runs Bemanning, or Consulting with recruiting on.

404 This job is not open for applications

The job is unpublished, closed, outside its publish dates, or the address is wrong.

429 Too many requests from this address

Wait for the time in Retry-After, then cache the list on your side.

No job.updated arrives

  1. Check that the webhook has job.updated, or no events picked.
  2. Check that the job was published before and after the save. A draft that is published sends job.published.
  3. Check that a listed field changed. Saving the same text sends nothing.
Jobs
GET https://api.lumenbase.io/functions/v1/v1-public-jobs?workspace=
Applications
POST /v1-public-job-applications
Webhooks
SettingsWorkspaceIntegrationsWebhooks
Without code
Jobs embed

Frequently asked questions

Do I need an API key to list my jobs?

No. GET https://api.lumenbase.io/functions/v1/v1-public-jobs?workspace=<your workspace address> returns what your career page already shows, to any website. Sending applications through the API needs a key with jobs:apply, used from your server.

How do I know when a job changes?

Add a webhook under Settings, Workspace, Integrations, Webhooks with job.updated. It is sent when a published job is saved with a change to what the ad shows, with the changed fields and their old values. Publishing and closing send job.published and job.closed.

Is there a webhook when an application changes stage?

Yes, application.stage_changed. It carries the new stage in data.record.stage and the old one in previous.stage, and is sent for every move, Hired and Declined included. Imports send none.

Was this article helpful?