The request
Reference for Get job, HeadHoncho API v1. It is a read, sent to the base address https://api.headhoncho.app.
GET /api/v1/jobs/{job_id}
The key or app needs the Jobs area at read. It counts as a read call: 300 a minute for each key or connected app. See rate limits.
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 |
What comes back
The job. Money is the price quoted, what was collected, and the profit after the subcontractor, each as a number in the company's currency. source is how the job was attributed: filled_by says whether the click came off a tracked call or the job's own record.
It never changes a record. It only reads the companies the key reaches.
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. |
| `expired_token` | 401 | That token has expired. Refresh it, or connect the app again. |
| `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. |
| `rate_limited` | 429 | Too many calls this minute. Wait and try again. |
Related
- 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 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.
- The same records in the app: the Jobs panel.
- How the API fits together: the model, API keys, errors and the MCP server.