HeadHoncho

Export jobs

Export jobs is a read in the HeadHoncho API. Jobs as a CSV file, newest first, up to 10,000 rows: ticket, technicians, status, dates, address, customer and price.

Read as Markdown

The request

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

GET /api/v1/jobs/export

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
statustext, in the queryNoA status name or slug from Who am I.scheduled
worker_idid, in the queryNoJobs this technician or subcontractor is on.wrk_3b90
fromdate, in the queryNoCreated on or after this day, in the company's time zone.2026-10-01
todate, in the queryNoCreated on or before this day.2026-10-31
leadstext, in the queryNoinclude (default), only, or exclude. One of include, only, exclude.include
bintext, in the queryNoopen (default), active or archived. Trash is never exported. One of open, active, archived.open

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

Over the API: the CSV itself (text/csv). Over MCP: a download link that works once for five minutes, so the file never passes through the AI. One row per job; the columns are the ones the app's own jobs export prints. With personal details hidden, names become initials, phones keep four digits and addresses are empty.

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
downloadobjectThe download.
download.urltextThe link.
download.expires_inwhole numberSeconds until the link stops working.
download.filenametextThe name of the file.

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 jobs: Jobs and leads in the companies this credential reaches, newest first, with status, technician, schedule, money and the ad click each came from.
  • Get job: One job or lead: who, where, when, which status, which technicians, the money on it and the ad click it came from.
  • Get job history: Everything that happened to a job, in order, with who did it: created, moved, assigned, noted, paid. The same log the job page shows.
  • Get job log: A job's timeline in plain words, one line per thing that happened: notes, moves, texts, money, the rules and the AI, each with who did it.
  • List situations: The situations the AI dispatcher is working on jobs now: what came up, the plan, and which step it is on.
  • List job photos: The photos stored on a job, oldest first, each with a link that opens it for one minute.
  • Get photo: One stored photo and a fresh link to its file. The link works for one minute.
  • Get calendar: Every job with a booked time between two days, earliest first. Canceled and closed jobs are left out, as on the app's calendar.
  • List unscheduled jobs: Open jobs and leads that have no booked time yet, the ones that waited longest first.
  • Search jobs: Find jobs by ticket number, customer, address or technician name, and technicians by name.
  • Get automatic status: Whether a person set this job's status by hand, why its facts do not hold it, and where Back to automatic would put it.
  • Get job detour: Whether a job is on a detour, such as Waiting on parts, and where Resolve would put it.
  • List job reassignments: The times this job was handed from one technician to another, oldest first, and how far each one got.
  • List calendar reassignments: Every reassignment on a job booked in a window: open ones, and ones that closed today.
  • The same records in the app: the Jobs panel.
  • How the API fits together: the model, API keys, errors and the MCP server.