AI builder

Jobo for Base44

A job board from a prompt, on live data.

Base44 builds an app from a description, and Jobo supplies the jobs. The generated app calls Jobo's REST API from a backend function, with your API key stored in Base44's Secrets so it never reaches the browser. Base44'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.

Base44 logoBase44How the pieces connect
API
https://connect.jobo.world
Auth
X-Api-Key header
Key stored in
Secrets
Called from
a backend function
MCP for the agent
Supported

What can you do with the Base44 integration?

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

01

Real listings from the first prompt

The app Base44 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 Base44's Secrets and is read by a backend function. 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

Base44'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 Base44 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 Base44's Secrets

    In the app editor, click Dashboard, then Secrets, then Add Secret. Name it JOBO_API_KEY, paste the key as the value and click Add Secret. The Secrets page only appears once the app uses backend functions, so ask the chat to create one first if it is missing.

  3. 3

    Prompt the build

    Tell Base44 what to build and where the data comes from. The call must run in a backend function, 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 Base44

    Click your workspace name, then Account settings, then Builder, and scroll to MCP Connections. Click Add custom MCP, enter a name and the server URL, choose OAuth as the authentication, then click Authorize & Add and sign in. The server URL is https://jobs-mcp.jobo.world/mcp, and you sign in with your Jobo account rather than a key. MCP connections need the Builder plan or higher.

  5. 5

    Publish

    Publish the app. Publish again after changing a secret: the published app keeps the values from the last publish.

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

The things people actually hit when running Jobo in Base44.

The API key is visible in the browser
The generated code is calling Jobo from the page. Ask Base44 to move the call into a backend function 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 Base44 documents it: a custom MCP server gives tools to Base44's own agent while it builds, not to the app it generates. The app reads jobs through the REST API.
Pasting the key into the chat did not save it as a secret
Base44 only auto-saves keys from a fixed list of providers when they are pasted into chat. Add the Jobo key on the Secrets page instead.

How do you get the most out of Base44?

  • 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 Base44

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