canonical: https://jentic.com/apis/arbeitsagentur.de/arbeitsagentur

# Arbeitsagentur De Arbeitsagentur Jobsuche API

Jentic publishes the only available OpenAPI specification for Arbeitsagentur Jobsuche API, keeping it validated and agent-ready. The Arbeitsagentur Jobsuche API exposes job listings from the German Federal Employment Agency (Bundesagentur für Arbeit), one of the largest single sources of vacancies in the German-speaking labour market. The API supports filtered searches by keyword, location, occupation, and other facets, with both web and mobile-app variants. It also exposes employer logo retrieval keyed by a hashed employer identifier.

## For AI agents

Search German Federal Employment Agency job listings by keyword, location, and occupation, and fetch employer logos.

## Scope

Does not handle applicant tracking, application submission, or candidate messaging - use for searching German Federal Employment Agency job listings only.

## Capabilities

- Search Bundesagentur für Arbeit job listings by keyword and filters
- Filter vacancies by location, employment type, and occupation
- Use the mobile-app variant to retrieve listings with the same filter shape
- Fetch the employer logo image for a vacancy using its hash identifier
- Aggregate German labour market vacancy counts by region or occupation

## Use cases

### Job Search for Candidates Targeting Germany

Surface vacancies from the German Federal Employment Agency for candidates relocating to or already living in Germany. Job-board aggregators and career assistants use this to give German-market coverage that complements private boards. The /pc/v4/jobs endpoint accepts keyword, location, and occupation filters and returns matching listings with metadata.

Example prompt: Call GET /pc/v4/jobs with the user's keyword and city, then return the top 10 matching listings with title, employer, and location.

### Labour Market Analytics Feeds

Pull aggregate vacancy counts over time to power labour market dashboards and economic research. Recruitment data products and policy researchers use Arbeitsagentur as a primary source for German job demand. The same /pc/v4/jobs endpoint supports filters that can be used to slice by occupation, region, or contract type.

Example prompt: Run repeated GET /pc/v4/jobs queries by occupation code and aggregate the result counts into a daily vacancy time series.

### Employer Branding in Job Listings

When rendering Arbeitsagentur listings inside a third-party UI, fetch the employer logo by its hash identifier so the listing matches the original branding. Career sites use this to make vacancies look native rather than text-only. The GET /ed/v1/arbeitgeberlogo/{hashID} endpoint returns the binary image for the employer.

Example prompt: For each listing in a search result, call GET /ed/v1/arbeitgeberlogo/{hashID} with the employer hashID and embed the returned image alongside the listing.

### AI Agent Job Search via Jentic

A career assistant agent helping a user explore the German job market can call Arbeitsagentur through Jentic to fetch vacancies that match the user's profile. The agent searches for the job-search operation, loads the schema, and executes with the user's keywords and location. Jentic resolves the API key from its credential vault.

Example prompt: Use Jentic search 'search German job listings', load the schema for GET /pc/v4/jobs, then execute with the user's keyword and location and return the top results.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /pc/v4/jobs | Search job listings |
| GET | /pc/v4/app/jobs | Search job listings (mobile variant) |
| GET | /ed/v1/arbeitgeberlogo/{hashID} | Get employer logo image |

## Key resources

- **Job Search** — Search Bundesagentur für Arbeit vacancies via web and mobile variants of the same endpoint
- **Employer Logos** — Fetch the employer logo image keyed by a hashed employer identifier

## Why Jentic

- **Setup:** Wiring the Arbeitsagentur Jobsuche API by hand means learning its X-API-Key scheme against the rest.arbeitsagentur.de host and building its job-search query paths yourself. Through Jentic you install once, import the Arbeitsagentur Jobsuche API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The job-search operations are read-only and the employer-logo path carries a hashID in the URL, so you limit the agent to the lookup operations it needs, such as searching job listings. You choose the operations it may call, so the agent only runs the read operations you have added.
- **Credential handling:** Your Arbeitsagentur API key is stored once, encrypted, by your own Jentic One instance and injected as the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search German job listings', and Jentic returns the matching Arbeitsagentur operation with its input schema so the agent calls the right endpoint without browsing docs.

## Related APIs

- **Adzuna API** — Global job-board aggregator covering Germany among 20+ markets, useful where multi-country reach matters more than direct Bundesagentur sourcing.
- **The Muse Jobs API** — Editorial job board with a strong tech employer mix, contrasting with Arbeitsagentur's broad public-employment-agency feed.
- **USAJobs API** — US federal-government counterpart to Arbeitsagentur for cross-border or comparative labour-market workflows.

## FAQ

### Why is there no official OpenAPI spec for Arbeitsagentur Jobsuche API?

Arbeitsagentur does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Arbeitsagentur Jobsuche API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Arbeitsagentur Jobsuche API use?

The API uses an API key sent in a custom header named X-API-Key. Through Jentic, the API key is stored encrypted in the vault and never enters the agent's context - Jentic injects the header at request time.

### Can I filter vacancies by city or postal code?

Yes. GET /pc/v4/jobs accepts location filters including a where parameter that takes a city name or postal code, plus radius and occupation filters that narrow the result set.

### What is the difference between /pc/v4/jobs and /pc/v4/app/jobs?

Both endpoints search the same underlying vacancy index. /pc/v4/jobs is the web variant used by jobsuche.arbeitsagentur.de and /pc/v4/app/jobs is the mobile-app variant; the response shapes differ slightly.

### What are the rate limits for the Arbeitsagentur API?

The OpenAPI spec does not declare explicit rate limits. Arbeitsagentur enforces fair-use limits per API key - sustained traffic above a few requests per second can be throttled. Contact Arbeitsagentur to negotiate a higher quota for production workloads.

### How do I search for German jobs through Jentic?

Install Jentic with pip install jentic, search for 'search German job listings', load the schema for GET /pc/v4/jobs, then execute with your keyword and location filters. Jentic injects the API key automatically.

### Can I limit what my agent is allowed to do with the Arbeitsagentur Jobsuche API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and every operation here is a read-only lookup. You can add just the job-search calls, such as GET /pc/v4/jobs or its mobile variant GET /pc/v4/app/jobs, and leave out the employer-logo lookup at GET /ed/v1/arbeitgeberlogo/{hashID} if you do not need it. The agent can only call the operations you have added, so it stays limited to searching German Federal Employment Agency vacancies.