Jobo for Bubble
A job board from a prompt, on live data.
Bubble builds an app from a description, and Jobo supplies the jobs. The generated app calls Jobo's REST API from the API Connector, which runs on Bubble's server, with your API key stored in Bubble's API Connector so it never reaches the browser.
- API
- https://connect.jobo.world
- Auth
- X-Api-Key header
- Key stored in
- API Connector
- Called from
- the API Connector, which runs on Bubble's server
- MCP for the agent
- Not documented
What can you do with the Bubble integration?
Build a job board or sourcing tool in Bubble on live job data, with your API key kept server-side.
Real listings from the first prompt
The app Bubble generates shows live jobs collected from employer career sites, not placeholder rows you replace later.
The key stays server-side
Your API key lives in Bubble's API Connector and is read by the API Connector, which runs on Bubble's server. The browser calls your app, and your app calls Jobo.
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.
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.
How do you connect Bubble to Jobo?
One-time setup. After this, the data keeps itself current.
- 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
Add the key to Bubble's API Connector
Open the API Connector and click + New to add a collection named Jobo. Set the collection's Authentication to Private key in header, with X-Api-Key as the key name and your API key as the private key. Bubble then adds the header to every call in the collection and routes the calls through its own server.
- 3
Prompt the build
Tell Bubble what to build and where the data comes from. The call must run in the API Connector, which runs on Bubble's server, never in browser code. Jobo's docs have a longer prompt that covers filters, facets and error handling.
textAdd 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
Publish
Initialize each call before using it: Bubble sends one real request to read the response structure. Then deploy as usual. If you use a separate development key, put it in the collection's Development key value.
What goes wrong with Bubble, and how do you fix it?
The things people actually hit when running Jobo in Bubble.
- The API key is visible in the browser
- The generated code is calling Jobo from the page. Ask Bubble to move the call into the API Connector, which runs on Bubble's server and read the key from API Connector, 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.
- A value marked Private is still visible to users
- Private fields are only protected in a collection that uses a secure authentication method such as Private key in header. In a collection set to None or self-handled, they are exposed. Keep the key in the collection's authentication settings, not in a parameter.
- The call does not appear as a data source or an action
- Each call has a Use as setting. Data makes it available under Get data from an external API; Action makes it available in the workflow editor.
How do you get the most out of Bubble?
- 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.
- Add the search as a Data call for a repeating group of results, and tick Private on anything the page does not need to set.
Which other Jobo integrations work alongside Bubble?
Start pulling live jobs into Bubble
One API key covers every integration, and the same job index sits behind all of them.













