Submit answers
Auto Apply is an invite-only beta.
The one write in the application loop: submit the complete answer snapshot for the current answerable step.
Answers are validated synchronously against the step’s fields before anything touches the employer’s form. Invalid answers return 400 with per-field errors and cost nothing - no correction round is consumed.
Valid answers are accepted exactly once per (step, correction round). Jobo then fills the form and advances it - intermediate pages auto-continue and the final page auto-submits; the caller never chooses. The request BLOCKS until the next decision point: the next step’s fields (awaiting_answers with a new current_step), the same step back as a correction round (correction_round incremented, command_errors carrying what the employer’s ATS rejected), or the terminal result (submitted or failed). Keep your HTTP client timeout above 540 seconds.
Answer within the step’s answers_expire_at deadline (about 5 minutes; 60 seconds for one-time verification codes) - a live browser is holding the employer’s form open. Past it, most applications release their browser and keep waiting for your answers (answers_expire_at becomes null; the overall queue timeout still applies, and resuming takes a little longer while a fresh browser picks the form back up). Verification-code steps, and providers that cannot resume on a fresh browser, instead fail with verification_timeout / answers_timeout.
A repeated POST for an already-accepted round attaches to the in-flight wait instead of erroring (its payload is ignored), so retrying after a dropped connection is safe.
Authorizations
API key provided by Jobo
Path Parameters
Application ID.
Body
The complete answer snapshot for the application's current answerable step. Validated synchronously; accepted exactly once per (step, correction round).
Response
The next decision point: the next step's fields, a correction round on the same step, or the terminal result.
Version of the profileless Auto Apply API contract.
2026-08-31 "2026-08-31"
Stable application ID.
Supplied Jobo job ID, or null when apply_url was supplied directly.
Resolved application URL.
Stable provider identifier selected at intake.
Provider display name captured at intake.
Current durable application state.
queued, running, awaiting_answers, submitted, failed, canceled Whether cancellation has been requested.
submitted_at, failed_at, or canceled_at, whichever is set.
Provider implementation version captured at intake.
Non-sensitive request or submission identifier issued by the provider, suitable for support tracing when present.
256Authoritative evidence used to confirm the submitted state.
provider_receipt, confirmation_page Actor that completed cancellation, when applicable.
The step currently awaiting answers - the one to answer next. Null while the application is queued, running between steps, or terminal.

