Skip to main content
A sandbox key (jbe_test_…) returns fictional data for free. The base URL (https://connect.jobo.world), request bodies, and response shapes are the same as live: only the key changes. It serves search, job and company lookups, and Auto Apply (supported endpoints).
To create one, open Developers → API Keys in the dashboard, select Create key, and choose Sandbox under Key type. Sandbox keys count toward your account’s limit of 5 active API keys.

What is different

In sandbox responses:
  • Every response carries X-Jobo-Environment: sandbox.
  • Every job has source: "jobosandbox". Its apply_url is a working form on the Jobo sandbox ATS at sandbox.jobo.world, so POST /api/auto-apply/applications with a sandbox job_id runs a real application end to end.
  • The sandbox emails each submission, with the resume attached, to the address entered in the form. Use an inbox you control.
  • Dates move forward every day, so the newest posting is always recent and posted_after windows behave as on live.
  • Job and company IDs are stable and safe to store.

Supported endpoints

Any other endpoint answers 404 with code: "not_available_in_sandbox". Use a live key for feeds (including managed and saved feeds, and expired jobs), occupations, geocoding, domain lookups, and connecting or deleting a mailbox.

Occupations

The sandbox does not support occupations yet:
  • Sandbox jobs carry no occupation, and GET /api/occupations answers 404 not_available_in_sandbox.
  • On POST /api/jobs/search, the job_categories, job_subcategories, and occupation_ids filters are not applied. The response is unfiltered and carries an unknown_request_fields warning.
  • The job_categories, job_subcategories, and occupations facets are not returned.
Test occupation filters with a live key.

Brands

Sandbox jobs never carry brand. Test brand handling with a live key.

Keeping live and sandbox apart

  • IDs do not cross over. A live job ID is unknown to a sandbox key, and a sandbox application answers 404 application_not_found to a live key (and the other way round).
  • With a sandbox key, apply_url must be a https://sandbox.jobo.world/apply/… form. Anything else returns 422 invalid_target.
  • Auto Apply idempotency keys are scoped to your account. Reusing a live-key create’s key on a sandbox-key create, or the other way round, returns 409 idempotency_key_reuse. See Idempotency.
  • Mailboxes belong to your account, not to an environment, so one connected with a live key also serves sandbox applications.
  • Every mailbox endpoint returns 403 auto_apply_not_enabled until Jobo enables Auto Apply for your account, even in the sandbox. Until then, read the sandbox’s emailed codes from your own inbox and submit them as answers.
Sandbox applications run real browser sessions and share your account’s Auto Apply concurrency and daily limits with live applications. A busy sandbox test run can hold back live applications.

Test scenarios

Named scenarios on the sandbox ATS test your Auto Apply loop and its recovery paths. They are not listed in search: create an application with a sandbox key and apply_url set to https://sandbox.jobo.world/apply/<slug>. Browse them at sandbox.jobo.world.

Next steps

The application loop

Create, answer, correct, and recover an Auto Apply application against these scenarios.

Quickstart

Run your first search and read the parts of the response every integration uses.