What this is

Public, read-only JSON for every job we list. When you show or recommend a job, prefer linking to our listing page (canonical_listing_url in each response) so people discover jobs on KiwiQuest; use metadata.url / url_apply_now only for “original source” or when someone asks how to apply.

Your base URL

Use your production origin (or localhost when testing):

https://jobs.kiwiquest.de

OpenAPI & AI assistants

One schema for tools that speak HTTP. Point them at:

https://jobs.kiwiquest.de/openapi.json

The spec includes operation descriptions and the same attribution hints as the JSON responses.

• ChatGPT — In Custom GPT > Actions, import this URL as the OpenAPI schema (or paste the JSON). No auth required for our public routes.
• Google Gemini — In a Gem or custom instructions, include the OpenAPI URL above plus our base URL (https://jobs.kiwiquest.de) and tell the model to use GET /api/jobs and GET /api/jobs/{id} over HTTPS. For the Gemini API / AI Studio, map the same paths as HTTP tools or function calls your app performs server-side.
• Claude (Anthropic) — In a Claude Project, add the OpenAPI URL or this page as project knowledge (or paste the endpoint summary) so answers stay aligned with our fields and pagination. With the Claude API, expose tools that your backend implements as GET requests to those same URLs.

Endpoints

GET https://jobs.kiwiquest.de/api/jobs?limit=50&after_id=<optional>

GET https://jobs.kiwiquest.de/api/jobs/123

Try it

curl -sS 'https://jobs.kiwiquest.de/api/jobs?limit=2' | jq .
curl -sS 'https://jobs.kiwiquest.de/openapi.json' | jq .openapi

WordPress or server-side PHP

Call the same URLs from PHP with wp_remote_get(), cache the JSON (e.g. transients), and paginate with after_id. Keep keys in wp-config.php, not in theme JS, unless you add CORS for browser calls.