Schedule follow up

The request

Reference for Schedule follow up, HeadHoncho API v1. It is a command, sent to the base address https://api.headhoncho.app.

POST /api/v1/commands/schedule-follow-up

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

It runs the app's own command schedule-follow-up. 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

Name	Kind	Required	Description	Example
`job_id`	id, in the JSON body	Yes	The job id, or its number.	`job_1138`
`due_at`	datetime, in the JSON body	Yes	ISO 8601. When to chase.	`2026-10-28T10:00:00-05:00`
`reason`	text, in the JSON body	No	Why it is open. Up to 200 characters.	`Waiting on the quote`

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) due_at (required, datetime) reason (optional, text)

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

What comes back

accepted, job_id, number, follow_up_id, status_id and position. A job on the line moves to Follow up, and a finished job reopens onto it. A job already on a detour keeps its status and gains one more stop.

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.

Field	Type	Meaning
`accepted`	true or false	True when the command ran. A command that cannot run is an error instead.
`job_id`	id (text)	The id of the job.
`number`	whole number	The number people say out loud, such as the job number.
`follow_up_id`	id (text)	The id of the follow up.
`status_id`	id (text)	The id of the status.
`position`	whole number	Where the change landed in the event log. Pass it as `after` on a read to see your own write.

Jobs, not the Leads panel

A follow-up belongs to a job. A lead that has been booked as a draft job takes one; a lead still in the Leads list does not.

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.
`read_only`	403	This credential may read this area but not change it.
`not_found`	404	No such record in the companies this credential reaches.
`invalid`	422	Some fields were refused. See fields.
`missing_idempotency_key`	400	Send an Idempotency-Key header on every command.
`idempotency_mismatch`	409	This Idempotency-Key was used with a different body.
`idempotency_in_progress`	409	A command with this Idempotency-Key is still running. Wait a moment and send it again.
`no_credits`	402	Out of credits. Top up on Settings › Credits, or turn on auto top-up.

Create lead: Add a lead to one company, the way a person adds one by hand. Send what you know; the rest can be filled in later.
Update lead: Change what a lead asked for: the customer, the address, the service, the time, the urgency or the notes. Only the fields you send change.
Mark lead lost: Close an open lead as lost, with the reason. It moves to Archive on the company's own clock.
Pass lead: Say a new lead is not yours to take, with an optional reason. It leaves the list to answer.
Book lead: Turn a lead into a job with everything the lead holds. The lead becomes won and is linked to the job.
Dismiss lead: Send a lead to Trash as a mistake. It counts nowhere and is erased after 30 days.
Review conversion: Decide an ad click the matcher would not guess at: pick the job it produced, or reject it. Only then does it reach the Google file.
Update follow up: Move the date of an open follow-up, or change why it is open.
Resolve follow up: Say the chase happened. The follow-up is closed, and the job goes back to the line when it was the last stop.
Cancel follow up: Call off a follow-up that should never have been booked. It is removed, and no chase is recorded.
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

{
  "accepted": true,
  "job_id": "job_1138",
  "number": 1138,
  "follow_up_id": "fup_31a7",
  "status_id": "st_09",
  "position": 88640
}

curl -X POST "https://api.headhoncho.app/api/v1/commands/schedule-follow-up" \
  -H "Authorization: Bearer hh_live_..." \
  -H "Idempotency-Key: 6f1d2c9e-1b7a-4c1e-9a52-0d3f8e4b7a10" \
  -H "Content-Type: application/json" \
  -d '{
  "job_id": "job_1138",
  "due_at": "2026-10-28T10:00:00-05:00",
  "reason": "Waiting on the quote"
}'

import requests
import uuid

response = requests.post(
    "https://api.headhoncho.app/api/v1/commands/schedule-follow-up",
    headers={
        "Authorization": "Bearer hh_live_...",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "job_id": "job_1138",
        "due_at": "2026-10-28T10:00:00-05:00",
        "reason": "Waiting on the quote",
    },
)
response.raise_for_status()
print(response.json())

const response = await fetch("https://api.headhoncho.app/api/v1/commands/schedule-follow-up", {
  method: "POST",
  headers: {
    Authorization: "Bearer hh_live_...",
    "Idempotency-Key": crypto.randomUUID(),
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "job_id": "job_1138",
    "due_at": "2026-10-28T10:00:00-05:00",
    "reason": "Waiting on the quote"
  }),
});
const data = await response.json();
console.log(data);

Tool: schedule_follow_up
Arguments: job_id (id, required), due_at (datetime, required), reason (text, optional)
Access: do on Jobs
Hints: readOnly=false, destructive=false, idempotent=false, openWorld=false
Try asking: "Using HeadHoncho, schedule follow up with job_id job_1138 and due_at 2026-10-28T10:00:00-05:00 and reason Waiting on the quote."