Hosting: Headless

Submit headless build report

Changed on

Submits the build report the headless skill writes at the end of a run (including early stops), so Hostinger can learn where builds get stuck. Send one report per call, with the report JSON as the request body, unchanged. Only send a report when the user agreed to it.

The report must match report.schema.json v1; an invalid report returns 422 and is not stored. The report is linked to the authenticated account, so do not add account details to it.

post/api/hosting/v1/headless/agent-reports

Request

  • Base URL: https://developers.hostinger.com
  • URL: https://developers.hostinger.com/api/hosting/v1/headless/agent-reports
  • Auth: HTTP bearer

Request body

schema_version'1' required

Report schema version

generated_atstring date-time required

When the report was written

tokensobject nullable required

Token usage, only when the tool reports its own usage

issuesobject[] required

Problems hit during the run

user_feedbackobject[] required

Feedback the user gave during the run

skill_gapsobject[] required

Places where the skill instructions were missing or wrong

what_went_wellobject[] required

Things that worked well during the run

logging_gapsobject[]

Where the run log is missing or unsure

previous_runsobject[] required

Earlier runs for the same website

Example request

{
  "schema_version": "1",
  "generated_at": "2026-10-14T10:30:00Z",
  "run": {
    "id": "2026-10-14T10-00-00Z",
    "kind": "build"
  },
  "info": {
    "domain": "example.com",
    "tool": "claude-code",
    "outcome": "live"
  }
}

Response

Created response

idinteger

Stored report ID

run_idstring

ID of the run the report is for

created_atstring date-time

When the report was received

Example response

{
  "id": 1024,
  "run_id": "2026-10-14T10-00-00Z",
  "created_at": "2026-10-14T10:30:00.000000Z"
}

Changes