AI builder

Jobo for Lovable

A job board from a prompt, on live data.

Lovable builds an app from a description, and Jobo supplies the jobs. The generated app calls Jobo's REST API from a server function (an Edge Function in older projects), with your API key stored in Lovable's Secrets so it never reaches the browser. Lovable's agent can also connect to Jobo's MCP server, which lets it look at real listings while it builds; that connection is for the agent, not for the published app.

Lovable logoLovableHow the pieces connect
API
https://connect.jobo.world
Auth
X-Api-Key header
Key stored in
Secrets
Called from
a server function (an Edge Function in older projects)
MCP for the agent
Supported

What can you do with the Lovable integration?

Build a job board or sourcing tool in Lovable on live job data, with your API key kept server-side.

01

Real listings from the first prompt

The app Lovable generates shows live jobs collected from employer career sites, not placeholder rows you replace later.

02

The key stays server-side

Your API key lives in Lovable's Secrets and is read by a server function (an Edge Function in older projects). The browser calls your app, and your app calls Jobo.

03

Filters the API already has

Location, work model, employment type, experience level, skills, salary and posting date are request parameters, so the builder wires up filter controls instead of inventing its own matching.

04

A prompt that carries the contract

The search integration prompt in Jobo's docs spells out the request shape and the mistakes that still return 200, which a builder's agent otherwise gets wrong.

05

Live job search while you build

Lovable's agent can connect to Jobo's MCP server and look at real listings and valid filter values as it writes the app.

How do you connect Lovable to Jobo?

One-time setup. After this, the data keeps itself current.

  1. 1

    Create a Jobo API key

    Sign up, open Developers → API Keys in the Jobo dashboard and create a key. New accounts start with a $5 balance and need no credit card. A sandbox key returns fictional jobs for free while you build.

  2. 2

    Add the key to Lovable's Secrets

    When Lovable's agent needs a key it shows an Add secret form in the project chat; enter the key there, not in a chat message. To add it yourself, open More → Settings → Secrets in the project toolbar, select Add secret and name it JOBO_API_KEY. Secret values are write-only.

  3. 3

    Prompt the build

    Tell Lovable what to build and where the data comes from. The call must run in a server function (an Edge Function in older projects), never in browser code. Jobo's docs have a longer prompt that covers filters, facets and error handling.

    text
    Add job search to this app using the Jobo API.
    
    - Call POST https://connect.jobo.world/api/jobs/search from server-side code only.
    - Send my key from the JOBO_API_KEY secret in the X-Api-Key header. Never expose it to the browser.
    - Request body: {"queries": ["<keywords>"], "locations": ["<place>"], "page": 1, "page_size": 20}.
    - The response has a "jobs" array and a "total". Show title, company.name, locations and date_posted, and link each job to its listing_url.
    - Add keyword and location inputs and pagination. On HTTP 402 show "out of credits" instead of retrying.
  4. 4

    Optional: connect Jobo's MCP server to Lovable

    Open Connectors, select Add custom and choose MCP server. Enter a server name and the server URL, keep OAuth as the authentication, then click Add & authorize and complete the browser sign-in. The server URL is https://jobs-mcp.jobo.world/mcp, and you sign in with your Jobo account rather than a key. Each workspace member connects with their own sign-in, and a workspace admin can switch custom MCP servers off.

  5. 5

    Publish

    Publish the app as usual. The server function reads the secret at run time, so there is nothing else to copy across.

What goes wrong with Lovable, and how do you fix it?

The things people actually hit when running Jobo in Lovable.

The API key is visible in the browser
The generated code is calling Jobo from the page. Ask Lovable to move the call into a server function (an Edge Function in older projects) and read the key from Secrets, then create a new key in the Jobo dashboard and delete the exposed one.
A filter returns no jobs
Filter values are lowercase, hyphenated and matched exactly, and an unrecognised value is not an error. Check them against the documented values: full-time rather than full_time, onsite rather than on-site.
Searches start failing with HTTP 402
The balance cannot cover the request. Search is billed per job returned, so a results page of 20 jobs costs 20 jobs. Top up, or lower page_size.
The published app cannot use the MCP connection
That is how Lovable documents it: a custom MCP server gives tools to Lovable's own agent while it builds, not to the app it generates. The app reads jobs through the REST API.
Lovable rejects the secret name
Names starting with VITE_, SUPABASE_ or LOVABLE_ are reserved. JOBO_API_KEY works.

How do you get the most out of Lovable?

  • Build against a sandbox key first. It returns fictional jobs for free, so a prompt that loops on a broken request costs nothing.
  • Keep page_size at what the page shows. Search bills every job returned, not every job displayed.
  • Cache results for repeated searches rather than calling the API on every page view.

Start pulling live jobs into Lovable

One API key covers every integration, and the same job index sits behind all of them.