Arbeitsagentur Jobs Scraper

Scrape job listings from Germany's Federal Employment Agency (Bundesagentur für Arbeit — arbeitsagentur.de), the country's largest official job board, via its public Jobsuche API. No login, no account, no CAPTCHA.

What you get

For every job (one dataset row, one PPE charge):

Field	Description
title, profession	Job title and vocational category
company, employer_hash	Employer name and stable employer id
location, postal_code, street, region, country	Full workplace address
latitude, longitude, distance_km	Geo-coordinates and radius distance
description	Full job description (markdown)
contract_type	Employment / Apprenticeship / Self-employment / Internship
compensation	Stated salary / pay, when available
work_modes, full_time	Full-time / part-time / shift / home-office flags
contract_duration, temporary_work, minor_employment	Contract details
disability_friendly, career_change_friendly	Suitability flags
all_locations	Every workplace location on the posting
published_date, first_published_date, modified_date, entry_date	Timeline
external_url, job_url	Links to the posting

Input

• Search keywords — one or more German keywords (e.g. Elektroingenieur, Softwareentwickler). Leave empty to browse all jobs in a location.
• Location — city or region (e.g. Berlin, München), with a radius (km).
• Job type — Employment / Apprenticeship / Self-employment / Internship.
• Fetch full job details — on by default; adds the full description, salary and contract fields (one extra request per job).
• Max items / Max pages per keyword — result caps.
• Proxy — Apify Proxy, RESIDENTIAL group, country DE (default).

Pricing

Pay-per-event: you are charged once per job record delivered to the dataset. The actor runs on your own Apify account and proxy — no extra keys required.

How it works

The actor calls the official Jobsuche search endpoint, paginates the results, and (optionally) fetches each job's detail document for the full description and salary. All requests go through the Apify RESIDENTIAL proxy from the first byte. This is a documented public API — the actor performs no login and stores no credentials.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.