HeadHoncho

List needs you

List needs you is a read in the HeadHoncho API. Jobs that wait on a person, most urgent first, each with the reasons: no technician, unpaid cut, no answer and more.

Read as Markdown

The request

Reference for List needs you, HeadHoncho API v1. It is a read, sent to the base address https://api.headhoncho.app.

GET /api/v1/needs-you

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

Send your key as Authorization: Bearer hh_live_.... See API keys.

Parameters

NameKindRequiredDescriptionExample
company_idid, in the queryNoOne company. Default: every company the credential reaches.cmp_14f5
limitnumber, in the queryNo1 to 200. Default 50.50
pagenumber, in the queryNoPage number, from 1.1

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

items, most urgent first: job (in the Get a job shape), band (now, today or later), due_at (when the harm lands) and reasons. Each reason has slug, label, severity (danger or warn), verb (the one thing that clears it), band and due_at. count is how many jobs wait in all. Jobs in Trash or Archive never appear.

It never changes a record. It only reads the companies the key reaches.

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
itemslist of objectsThe rows on this page.
items[].jobobjectThe job.
items[].job.idid (text)The id of this record. Ids are opaque text: keep them exactly as given.
items[].job.numberwhole numberThe number people say out loud, such as the job number.
items[].job.statusobjectThe job status.
items[].job.status.idid (text)The id of this record. Ids are opaque text: keep them exactly as given.
items[].job.status.nametextThe name, as the app shows it.
items[].job.status.slugtextThe same name as a lowercase code word. Match on this, not on the name.
items[].job.technicianslistThe technicians.
items[].bandtextThe band.
items[].due_attime (ISO 8601, with offset)When the due happened. Carries its offset from UTC; Z is UTC.
items[].reasonslist of objectsThe reasons.
items[].reasons[].slugtextThe same name as a lowercase code word. Match on this, not on the name.
items[].reasons[].labeltextThe name the app shows for it.
items[].reasons[].severitytextThe severity.
items[].reasons[].verbtextThe verb.
items[].reasons[].bandtextThe band.
items[].reasons[].due_attime (ISO 8601, with offset)When the due happened. Carries its offset from UTC; Z is UTC.
countwhole numberHow many match in all, across every page.

Same reasons as the app

The reasons are the app's own catalogue, read with the same rules the Needs you list uses. Reasons a workspace has not switched on are left out, as they are in the app.

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.
`not_found`404No such record in the companies this credential reaches.
`out_of_scope`404No such company in the companies this credential reaches.
`invalid`422Some fields were refused. See fields.
`no_credits`402Out of credits. Top up on Settings › Credits, or turn on auto top-up.
  • List leads: Leads in the companies this credential reaches, newest first, with stage, service, estimate and where each came from.
  • Get lead: One lead: who, what and when they asked for, the estimate, its stage and what happened to it so far.
  • List conversion reviews: Ad clicks the matcher would not guess at. Each waits for you to pick the job it produced, or to reject it.
  • The same records in the app: the Jobs panel.
  • How the API fits together: the model, API keys, errors and the MCP server.