bundesAPI / bundesAPI/jobsuche-api

Question regarding contact information hidden behind captcha protection

Open
#68 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
153
Forks
23
PR merge metrics
No merged PRs in 30d

Description

## Description

We are a non-profit educational organization in Germany and currently develop an **internal application** assistant for job seekers.

Our application uses the Jobsuche API to identify suitable job offers and generate application documents for participants.

We noticed that contact information is available for many job postings, but for a significant number of offers the contact details seem to be protected behind captcha-based mechanisms on the Arbeitsagentur platform and are therefore not available through the API.

We are **not interested in bypassing any protection mechanism**.

Our questions are:

1. Is there an official way to obtain employer contact information for these job postings?
2. Are there plans to expose additional contact information through the API?
3. Is there an official contact person or product owner for questions regarding the Jobsuche API?
4. How are third-party integrations expected to handle job applications if contact information is not available through the API?

Our goal is to support job seekers and educational participants in creating and sending applications in a legally compliant way.

Any guidance would be greatly appreciated.

### Additional question

Has a verification-based access model for trusted organizations ever been considered?

This could allow educational providers, public institutions or non-profit projects to access additional information while maintaining appropriate safeguards against anonymous mass crawling.

Thank you.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by reviewing the Jobsuche API's existing contact-information behavior and access guidance, then identify the official response for employer-contact availability, third-party applications, verification-based access, and API ownership; done means a maintainer or product owner provides authoritative guidance rather than a code change.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.