Public jobs API | Lexgo.lu

Unauthenticated read API for live Belgian and Luxembourg legal jobs, function names, and upcoming scheduled events. v1 is additive-only; breaking changes need a new version. See versioning and deprecation.

Send candidates to click_url (the LexGO page with tracking). url is the untagged canonical page; job and event ids accept either. There is no apply-via-agent. Search is compact (no body). GET /api/v1/jobs/{id} / MCP get_job return a sanitized plaintext description. Raw HTML, emails, phones, and ATS URLs are stripped. Permitted use is in the Terms and conditions.

REST

Live vacancies, function names, taxonomies, and upcoming scheduled events. No API key.

GET /api/v1/jobs Search live vacancies
GET /api/v1/jobs/{id} Sanitized description and structured facets. Integer, id-slug, or an allowlisted lexgo.be/lu job URL. Call this before recommending.
GET /api/v1/functions Function names
GET /api/v1/taxonomies Function, discipline, region, and work-environment ids plus experience / contract / arrangement enums. Use these ids as search filters.
GET /api/v1/events Upcoming scheduled events
GET /api/v1/events/{id} One upcoming event

Limits and availability

60 requests / minute / IP and 600 / minute globally on the REST and MCP paths. Responses send IETF RateLimit and RateLimit-Policy headers. JSON 429 is RFC 9457 application/problem+json with Retry-After.
REST GET sends Cache-Control: private, no-cache and an ETag on job list and show. If-None-Match may return 304. MCP POST stays Cache-Control: private, no-store.
A kill switch returns JSON 503 unavailable and does not query the database.
Unknown /api paths return the same problem+json 404. Errors include a machine-readable code.

MCP

POST /mcp JSON only. The same jobs, functions, taxonomies, and events as REST. Call get_job before recommending a vacancy. GET /mcp is 405; there is no SSE.

MCP discovery: /.well-known/mcp and /.well-known/mcp/server-card.json. A compatibility copy lives at /mcp-server-card.json.

Machine-readable docs

Versioning and deprecation
OpenAPI JSON (GET /openapi.json)
OpenAPI YAML (GET /api/openapi.yaml)
RFC 9727 API catalog (GET /.well-known/api-catalog)
AI catalog (GET /.well-known/ai-catalog.json)
Agent site guide (llms.txt)

REST

Live vacancies, function names, taxonomies, and upcoming scheduled events. No API key.

Limits and availability

MCP

Machine-readable docs

Don't miss anything