Post v1feedback
Submit a bug report or product feedback. The report is persisted first and then surfaced to the hiloop team; a delivery problem on the surfacing side never fails the request. Repeat submissions with the same fingerprint (supplied, or content-derived when omitted) return the original report instead of storing a duplicate, so retries are safe.
Authorizations
Hiloop API key sent as an HTTP Bearer token.
Body
A short summary of the report. Required; at most 300 characters.
The product surface the report is about. Required; one of cli, api, web, sandbox,
telemetry, annotations, docs, or other.
How severe the problem is. Optional; one of critical, high, medium, or low. Leave it
empty for general feedback that is not a bug.
Free-form feedback text. Optional; at most 10,000 characters.
What was expected to happen. Optional; at most 10,000 characters.
What actually happened. Optional; at most 10,000 characters.
Steps to reproduce the problem. Optional; at most 10,000 characters.
Correlation keys — run, event, or artifact ids — linking the report to recorded telemetry. Optional; at most 50 entries, each at most 256 characters.
A stable, content-derived deduplication key (for example <surface>/<short-slug>). Enforced:
a submission whose fingerprint already exists returns the original report's id instead of
storing (and surfacing) a duplicate, which makes retrying a lost response safe. When omitted,
the server derives one from the report's content, so re-sending an identical report also
converges. Optional; at most 300 characters.
The hiloop client version that produced the report. Optional; at most 100 characters.