HeadHoncho

Put back job

Put back job is a command in the HeadHoncho API. Let a held-back job count in the technician's next balance close again.

Read as Markdown

The request

Reference for Put back job, HeadHoncho API v1. It is a command, sent to the base address https://api.headhoncho.app.

POST /api/v1/commands/put-back-job

The key needs the Money area at do. An answered call costs 1 credit; a refusal costs nothing. See credits.

It runs the app's own command put-back-job. Send an Idempotency-Key header with every call: the same key with the same body returns the first answer and runs nothing twice. See the model.

Parameters

NameKindRequiredDescriptionExample
worker_idid, in the JSON bodyYesThe technician, from Who am I's technicians.wrk_7a12
job_idid, in the JSON bodyYesThe job id, or its number.job_1138

Try it with your key

Paste your key and change the values. The box builds the call as a cURL line and a fetch line, ready to copy. It never sends anything itself.

Your key stays in this page and is never sent anywhere. Copy the line below and run it yourself.

What comes back

accepted, worker_id, job_id, number, hold_id and position. A job that is not held back is refused by name.

It never deletes anything. It changes only what the command names, and it writes the change to the job's history with who asked for it.

Every field in the answer

Types are read from the example answer. Money is a plain number in the company's currency. A time carries its offset from UTC (Z is UTC). Ids are opaque text. A field with no line of its own here has its name spelled out; the common fields mean the same on every page.

FieldTypeMeaning
acceptedtrue or falseTrue when the command ran. A command that cannot run is an error instead.
worker_idid (text)The id of the worker.
positionwhole numberWhere the change landed in the event log. Pass it as after on a read to see your own write.
job_idid (text)The id of the job.
numberwhole numberThe number people say out loud, such as the job number.
hold_idid (text)The id of the hold.

Errors that apply

CodeStatusWhat it means
`missing_key`401Send your key as Authorization: Bearer hh_live_...
`unknown_key`401That key is not one we issued, or it was revoked.
`no_access`403This credential does not reach that. Ask the person who made it for access.
`read_only`403This credential may read this area but not change it.
`not_found`404No such record in the companies this credential reaches.
`invalid`422Some fields were refused. See fields.
`missing_idempotency_key`400Send an Idempotency-Key header on every command.
`idempotency_mismatch`409This Idempotency-Key was used with a different body.
`idempotency_in_progress`409A command with this Idempotency-Key is still running. Wait a moment and send it again.
`no_credits`402Out of credits. Top up on Settings › Credits, or turn on auto top-up.
  • Close balance: Close what a technician is owed for the jobs you name, or for everything open through a day, as one payout netted against the cash they hold.
  • Record payout: Record money paid to a technician, or paid in by one, that names no jobs. It moves their balance and closes no particular job.
  • Void closed balance: Undo a balance close or a payout entered wrong. Its jobs open again, and it stays on the list, marked voided, with why.
  • Hold back job: Keep one job out of a technician's balance closes until you put it back, with why. Its cut, parts and cash wait together.
  • Post monthly pay: Add a month of pay to the balance of every active technician on a monthly rate. A month is posted once, however often this is sent.
  • The same records in the app: the Finance panel.
  • How the API fits together: the model, API keys, errors and the MCP server.