List job photos

The request

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

GET /api/v1/jobs/{job_id}/photos

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

Name	Kind	Required	Description	Example
`job_id`	id, in the path	Yes	The 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 API key job_id (required, id)

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

What comes back

job (id and number), items and count. Each item is a photo: id, content_type, byte_size, stored_at, note_id (the note it sits under, or null) and url, a link that works for expires_in seconds. Ask again for a new link. With personal details hidden, url is left empty, because a photo can show a street or a face.

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.

Field	Type	Meaning
`job`	object	The job.
`job.id`	id (text)	The id of this record. Ids are opaque text: keep them exactly as given.
`job.number`	whole number	The number people say out loud, such as the job number.
`items`	list of objects	The rows on this page.
`items[].id`	id (text)	The id of this record. Ids are opaque text: keep them exactly as given.
`items[].content_type`	text	The content type.
`items[].byte_size`	whole number	The byte size.
`items[].stored_at`	time (ISO 8601, with offset)	When it was stored. Carries its offset from UTC; `Z` is UTC.
`items[].note_id`	value or null	The id of the note.
`items[].url`	text	The link.
`items[].expires_in`	whole number	Seconds until the link stops working.
`count`	whole number	How many match in all, across every page.

Photos the technician sent by text

A photo that came in on a text is counted on the job but never stored, so it is not listed here. Only photos someone uploaded are.

Errors that apply

Code	Status	What it means
`missing_key`	401	Send your key as Authorization: Bearer hh_live_...
`unknown_key`	401	That key is not one we issued, or it was revoked.
`no_access`	403	This credential does not reach that. Ask the person who made it for access.
`not_found`	404	No such record in the companies this credential reaches.
`invalid`	422	Some fields were refused. See fields.
`no_credits`	402	Out 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.
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.
Export jobs: Jobs as a CSV file, newest first, up to 10,000 rows: ticket, technicians, status, dates, address, customer and price.
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.

Answer cURL Python JavaScript Your AI

{
  "job": {
    "id": "job_1138",
    "number": 1138
  },
  "items": [
    {
      "id": "pho_5d21",
      "content_type": "image/jpeg",
      "byte_size": 2481220,
      "stored_at": "2026-10-16T11:42:10Z",
      "note_id": null,
      "url": "https://files.headhoncho.app/photos/pho_5d21.jpg?signature=k7Qm...",
      "expires_in": 60
    }
  ],
  "count": 1
}

curl "https://api.headhoncho.app/api/v1/jobs/job_1138/photos" \
  -H "Authorization: Bearer hh_live_..."

import requests

response = requests.get(
    "https://api.headhoncho.app/api/v1/jobs/job_1138/photos",
    headers={"Authorization": "Bearer hh_live_..."},
)
response.raise_for_status()
print(response.json())

const response = await fetch("https://api.headhoncho.app/api/v1/jobs/job_1138/photos", {
  headers: { Authorization: "Bearer hh_live_..." },
});
const data = await response.json();
console.log(data);

Tool: list_job_photos
Arguments: job_id (id, required)
Access: read on Jobs
Hints: readOnly=true, destructive=false, idempotent=true, openWorld=false
Try asking: "Using HeadHoncho, list job photos with job_id job_1138."