Answer a task
Answers the question of a task in waiting_input and lets it carry on. The answer must have text, files or both. Only tasks created with on_question: ask can wait. A key limited to some workspaces may only use those.
Requires the agent:write permission.
Authorizations
An API key from Settings → API keys, sent as Authorization: Bearer jb_live_…
Path Parameters
The task id.
1 - 64^[A-Za-z0-9-]+$Body
Your answer in words. Send text, files or both.
8000Ids of files from POST /v1/files to answer with, up to 20. The key also needs files:read.
201 - 64The question.id you are answering. If the task has moved on to another question, the answer is refused.
64Response
The task, back in the queue.
The task id.
Where the task is.
queued, running, waiting_input, succeeded, failed, cancelled Why the task is in this state: completed, cancelled, question, invalid_output, budget_exceeded, timed_out, goal_unreachable, worker_stopped, insufficient_credits or run_failed.
Whether the agent reports that the goal was met.
The result following your output_schema. Only set when the task succeeded and a schema was given.
The agent's final answer as text.
Files the agent made.
Ids of the files handed to the task.
What went wrong, for a failed task.
The id of the chat in the Jobbit app where the work happens.
The workspace key, if one was given.
The model the task runs on.
The effort level.
Whether the task may ask questions.
fail, ask The open question, while the status is waiting_input.
How many questions the task has asked.
The most credits the task may spend.
Your source labels.
When the task was created.
When it started running.
When it finished.