DEVELOPER PORTAL

Integrate your jobs with Jobiba

Choose the integration path that matches your system. The current platform supports employer feed configuration, feed preview and CSV/XLS/XLSX bulk upload workflows.

Read partner feed guide →

Jobiba for Claude, ChatGPT, Codex and Gemini (MCP)

Use Jobiba from your AI assistant: search live jobs, research salaries, tailor your CV to a job, apply after you confirm, prepare interviews and track applications. Employers can post and edit jobs, screen applicants, shortlist and contact candidates, and see plans, all in chat. Public tools (job search, salary research, offer analysis, company research, plans) work without signing in; personal and employer tools use Jobiba OAuth.

  • Full guide: every tool, example prompts and setup steps
  • MCP server URL: https://jobiba.com/mcp (Streamable HTTP)
  • Claude: Settings → Connectors → Add custom connector, or in Claude Code run claude mcp add --transport http jobiba https://jobiba.com/mcp
  • ChatGPT: Settings → Apps → Developer mode → Create app with the same URL.
  • Gemini CLI: gemini mcp add --transport http jobiba https://jobiba.com/mcp
  • Server card: /.well-known/mcp/server-card.json

Partner job feeds

For a system that can publish a job feed URL, use the Partner Feeds guide. It explains supported feed formats, recommended fields, validation and the feed lifecycle.

Supported feed formats

XML: Suitable for structured feeds with repeating job records. Jobiba's feed preview detects common job-list structures and suggests field mappings.
JSON: Suitable for API-style feeds where the payload is an array of job objects or contains a discoverable job array.
CSV: Supported as a feed format for configured employer feeds, while the employer bulk-upload workflow also accepts CSV, XLS and XLSX files with field mapping.
XLS/XLSX upload: Bulk spreadsheet upload is available through the employer workflow rather than as a remote feed URL.

Authentication & access

Employer feed configuration is authenticated through the employer account. API-key capabilities also exist in the employer backend, but credentials should only be used through the authenticated integration workflows exposed by the platform. Never publish an API key in a public repository or feed.

Designing a reliable integration

Publish stable HTTPS URLs where practical.
Keep job identifiers stable so updates can be matched to existing listings.
Provide complete titles and descriptions and a usable application URL.
Send current information and remove or deactivate closed positions according to the agreed feed lifecycle.

Technical help

For integration questions or a feed that cannot be parsed, use Contact Support and include the feed URL, format and a safe sample. Do not send secrets.